-
Notifications
You must be signed in to change notification settings - Fork 114
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Failed to Upgrade Calico v3.25.1 to v3.26.0 #716
Comments
Hi @kimullaa! Sorry to hear you're having trouble with the upgrade. Do you have a specific suggestion for how we can improve the docs here? This repo is just about documentation. Before we can begin to address this as a documentation problem, I suggest you take your problem to the Calico Users Slack channel. If it turns out that the failure can be fixed through documentation, we'll be happy to do what we can to help. |
Thanks.I posted this on Slack:https://calicousers.slack.com/archives/CPTH1KS00/p1686184117110149 |
@ctauchen We also found that |
@kimullaa Thanks for those details. I'll open a bug and we'll get this fixed. |
Fixed in this PR: #796. Closing out. |
I upgraded from calico v3.25.1 to calico v3.26.0 as described in "Upgrading an installation that uses manifests and the Kubernetes API datastore" but it failed. calico-node's status becomes
Init:CrashLoopBackOff
.calico-cni-plugin
is not created when executekubectl replace
. (calico-cni-plugin was added in v3.26.0 projectcalico/calico#7106 )so I think we need to changekubectl replace
tokubectl apply
.https://github.com/tigera/docs/blob/main/calico/operations/upgrading/kubernetes-upgrade.mdx?plain=1#L136The text was updated successfully, but these errors were encountered: