-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
🌱 KCP: remove code handling Kubernetes <= v1.21 #11146
Conversation
Signed-off-by: Stefan Büringer buringerst@vmware.com
/test ? |
@sbueringer: The following commands are available to trigger required jobs:
The following commands are available to trigger optional jobs:
Use
In response to this:
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-sigs/prow repository. |
/assign @chrischdi @fabriziopandini |
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
if err != nil { | ||
return errors.Wrapf(err, "unable to extract %q from Kubelet ConfigMap's %q", cgroupDriverKey, cm.Name) | ||
} | ||
data, ok := cm.Data[kubeletConfigKey] |
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.
wondering if the cgroup driver override can be removed at this point.
existing clusters were already mutated by this code, while for new clusters kubeadm does the defaulting.
it might be safer to do this once:
https://github.com/kubernetes/enhancements/blob/7e1c131dc50fa84caa5e99da2b8bf67db32054ab/keps/sig-node/4033-group-driver-detection-over-cri/kep.yaml
goes GA.
however CRs need to adapt it first too.
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.
Added it to #8190 (to consider this later)
LGTM label has been added. Git tree hash: 21b0c3b9b32aadc78473a17f28790b93bbdd0bd1
|
/test ? |
@sbueringer: The following commands are available to trigger required jobs:
The following commands are available to trigger optional jobs:
Use
In response to this:
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-sigs/prow repository. |
/test pull-cluster-api-e2e-conformance-ci-latest-main |
Pretty sure that these are independent (and known) flakes /retest |
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.
Nice cleanup!
/lgtm
BTW, I think we should start tracking deprecation stuff in a more efficient way, e.g.
- open tracking issues about things to deprecate when a CAPI version/a Kubernetes version/API version goes out of support
- might be add TODOs with a sort of naming convention so we can start searching across the codebase, e.g. TODO: Remove-After-K8s1.21 EOS
/retest |
@fabriziopandini @chrischdi @neolit123 Ready to merge? |
/lgtm |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: fabriziopandini 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 |
Signed-off-by: Stefan Büringer buringerst@vmware.com
What this PR does / why we need it:
While implementing #11137 we noticed some code in KCP that was only required for Kubernetes <= 1.21.
The min supported Kubernetes version of CAPI v1.9 will be v1.26, so dropping this now to reduce complexity
Which issue(s) this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)
format, will close the issue(s) when PR gets merged):Part of #8190