-
Notifications
You must be signed in to change notification settings - Fork 6.5k
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
Calico: use --allow-version-mismatch in calicoctl.sh to allow upgrades #7873
Calico: use --allow-version-mismatch in calicoctl.sh to allow upgrades #7873
Conversation
Hi @cristicalin. Thanks for your PR. I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/ok-to-test
Nice 👍
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: cristicalin, floryut The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/lgtm |
What type of PR is this?
/kind bug
What this PR does / why we need it:
Calico 3.20 introduced a feature to protect clusters from being modified by incompatible
calicoctl
versions. This has an impact in upgrading Calico from earlier versions to 3.20.The change proposed here modifies the wrapper used (
calicoctl.sh
) which in effect reverts back to the old behavior. An alternative would be to modify the calls tocalicoctl.sh
from our playbooks to add the--allow-version-mismatch
flag.Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
I submit this change to get some feedback on the two approaches and I'm open to moving to the alternative if reviewers see fit.
Does this PR introduce a user-facing change?: