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
Remove support for Kubernetes 1.20 #9384
Remove support for Kubernetes 1.20 #9384
Conversation
fe0a678
to
26c94b1
Compare
26c94b1
to
a9cb7e4
Compare
@xrstf I think we should also consider changing the default Kubernetes version to v1.22. |
@xmudrii I was thinking "always use the most recent supported version, minus 1", that's why i kep the default. No strong feelings either way. Convince me! 😁 |
3883bd4
to
e7cbc41
Compare
I've always understood that rule as the latest Kubernetes version, minus 1, not the latest supported in KKP (as long as n-1 is supported by KKP). Considering that 1.21 is entering the maintenance mode at the end of April, and reaching EOL at the end of June, I think we should start promoting/defaulting to 1.22. |
While rebasing I already changed the default in this PR 😁 |
419b05e
to
8907a63
Compare
/approve |
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.
/lgtm
/approve
LGTM label has been added. Git tree hash: 140b19ef9b5843e615871bd4c719cb3f2ef2da0f
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: floreks, xmudrii, xrstf 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 |
What does this PR do / Why do we need it:
Kubernetes 1.20 has gone EOL on February 28th, 2022. Time to remove it. This PR removes support for it, but configures an update rule to allow auto-updating all clusters to 1.21. To not run into errors when reconciling old clusters, most of the reconciling code can still handle 1.20 (e.g. the kubernetes-dashboard, etcd, ...). -- Those code places can be removed in a follow up KKP release when we're sure no 1.20 cluster exists anymore.
Does this PR introduce a user-facing change?: