-
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] call calico checks early on to prevent altering the cluster #8707
[calico] call calico checks early on to prevent altering the cluster #8707
Conversation
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: cristicalin 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 |
1cd7f39
to
4ee3b43
Compare
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.
It is nice to move calico checks into calico specific playbook file to make it simple.
Just one comment for typo.
(I don't want to block this with such small thing. I will put lgtm even if not updating)
4ee3b43
to
f38cf55
Compare
…with bad configuration
f38cf55
to
a73ebb4
Compare
Thank you for updating. /lgtm |
* master: metallb: Add images to downloads (kubernetes-sigs#8715) etcd: add etcd v3.5.3 for kubernetes 1.21+ (kubernetes-sigs#8712) [calico] call calico checks early on to prevent altering the cluster with bad configuration (kubernetes-sigs#8707)
…with bad configuration (kubernetes-sigs#8707)
…with bad configuration (kubernetes-sigs#8707)
…with bad configuration (kubernetes-sigs#8707)
call calico checks early on to prevent altering the cluster with bad configuration
What type of PR is this?
/kind feature
What this PR does / why we need it:
This PR ensures that calico checks are called early in the playbooks so that deployment fails before it makes bad changes to live clusters. Additionally this adds a migration procedure in the kubespray docs for folks migrating from 2.18 and hitting changing defaults.
Which issue(s) this PR fixes:
Fixes #8691
Special notes for your reviewer:
Does this PR introduce a user-facing change?: