Milestone to support Kubernetes v1.24 (support CRI compatibility) #1014
Labels
Comments
|
against, this is just a question, no pressure at all. |
|
@fujitatomoya Thank you for raising issue. I think OpenYurt v1.0.0 can support K8s v1.24, but we have not enough energy to verify it. Would you like to check the K8s v1.24 and add the new version for by the way, |
|
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
|
@fujitatomoya how about have a try for K8s v1.24 by the newest |
|
@rambohe-ch i was trying to verify with kubernetes version 1.24.9 with vanilla ubuntu22.04
root@cluster-master:~# apt-get install -qy --allow-change-held-packages --allow-downgrades kubelet=1.24.9-00 kubectl=1.24.9-00 kubeadm=1.24.9-00but meeting helm problem to install root@cluster-master:~/yurt-app-manager# helm install --debug --replace yurt-app-manager -n kube-system ./charts/yurt-app-manager --set image.tag=latest
install.go:192: [debug] Original chart version: ""
install.go:209: [debug] CHART PATH: /root/yurt-app-manager/charts/yurt-app-manager
client.go:128: [debug] creating 1 resource(s)
install.go:151: [debug] CRD nodepools.apps.openyurt.io is already present. Skipping.
client.go:128: [debug] creating 1 resource(s)
install.go:151: [debug] CRD uniteddeployments.apps.openyurt.io is already present. Skipping.
client.go:128: [debug] creating 1 resource(s)
install.go:151: [debug] CRD yurtappdaemons.apps.openyurt.io is already present. Skipping.
client.go:128: [debug] creating 1 resource(s)
install.go:151: [debug] CRD yurtappsets.apps.openyurt.io is already present. Skipping.
client.go:128: [debug] creating 1 resource(s)
install.go:151: [debug] CRD yurtingresses.apps.openyurt.io is already present. Skipping.
client.go:310: [debug] Starting delete for "yurt-app-manager-admission" ServiceAccount
client.go:128: [debug] creating 1 resource(s)
client.go:310: [debug] Starting delete for "yurt-app-manager-admission" ClusterRole
client.go:128: [debug] creating 1 resource(s)
client.go:310: [debug] Starting delete for "yurt-app-manager-admission" ClusterRoleBinding
client.go:128: [debug] creating 1 resource(s)
client.go:310: [debug] Starting delete for "yurt-app-manager-admission" Role
client.go:128: [debug] creating 1 resource(s)
client.go:310: [debug] Starting delete for "yurt-app-manager-admission" RoleBinding
client.go:128: [debug] creating 1 resource(s)
client.go:310: [debug] Starting delete for "yurt-app-manager-admission-create" Job
client.go:128: [debug] creating 1 resource(s)
client.go:540: [debug] Watching for changes to Job yurt-app-manager-admission-create with timeout of 5m0s
client.go:568: [debug] Add/Modify event for yurt-app-manager-admission-create: ADDED
client.go:607: [debug] yurt-app-manager-admission-create: Jobs active: 0, jobs failed: 0, jobs succeeded: 0
client.go:568: [debug] Add/Modify event for yurt-app-manager-admission-create: MODIFIED
client.go:607: [debug] yurt-app-manager-admission-create: Jobs active: 1, jobs failed: 0, jobs succeeded: 0
Error: INSTALLATION FAILED: failed pre-install: timed out waiting for the condition
helm.go:84: [debug] failed pre-install: timed out waiting for the condition
INSTALLATION FAILED
main.newInstallCmd.func2
helm.sh/helm/v3/cmd/helm/install.go:141
github.com/spf13/cobra.(*Command).execute
github.com/spf13/[email protected]/command.go:872
github.com/spf13/cobra.(*Command).ExecuteC
github.com/spf13/[email protected]/command.go:990
github.com/spf13/cobra.(*Command).Execute
github.com/spf13/[email protected]/command.go:918
main.main
helm.sh/helm/v3/cmd/helm/helm.go:83
runtime.main
runtime/proc.go:250
runtime.goexit
runtime/asm_amd64.s:1571 |
@fujitatomoya It looks like that yurt-app-manager image has caused this error. @kadisi would you be able to take a look for yurt-app-manager? |
|
Any update here? |
|
@YiuTerran not really, it's been a while, i probably should check with current master to see if the same problem can be observed. |
|
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What happened
Just a question about milestone to support Kubernetes v1.24 (support CRI compatibility)
What you expected to happen
Milestone / Development Schedule
How to reproduce it (as minimally and precisely as possible)
Not a problem since Kubernetes v1.24 is not supported.
Anything else we need to know?
We tried to use containerd only w/o dockerd, yurtadm failed to join the cluster from edge.
But with
--cri-socket=unix:///run/containerd/containerd.sockseems to make it work to join the edge node to the cluster.Motivation
others
/kind question
The text was updated successfully, but these errors were encountered: