-
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
Creating a v1.27.2 cluster on swap enabled host fails #8766
Comments
/triage accepted Thanks for filing this - I'm probably in favor of adding an inline patch to manage this for our CAPD templates as that's the way we tended to handle issues like this in the past - e.g. cgroup stuff. I don't think we should worry too much about the arg being deprecated until we have some idea about when it will be removed. |
I totally agree on this. I can file that PR to update if we agree on doing it that way: https://github.com/kubernetes-sigs/cluster-api/blob/main/test/infrastructure/docker/templates/clusterclass-quick-start.yaml and Two options there:
|
Let's do the ClusterClass JSON Patch IMO |
Should probably update our other ClusterClasses - those used for e2e tests etc. Even though we don't see this error in CI running those locally probably doesn't work right now. |
👍 on that. Just wanted to add that we can make it version dependent on the first variant, so we don't break possible old versions which don't have the flag. |
/assign |
Note: feature got introduced as alpha in kubernetes v1.22 kubernetes/enhancements#2400 |
+1 to going with a ClusterClass JSON patch + keeping our ClusterClasses as similar as possible Potentially we can replace this later if kubernetes/kubeadm#1682 is implemented before the command line flag is dropped. |
What steps did you take and what happened?
What did you expect to happen?
Cluster API version
main
Kubernetes version
v1.27.2
Anything else you would like to add?
CI is good because there's no swap there.
For kind node images <= v1.27.2, the
fail-swap-on
flag for the kubelet was always said.This flag got removed in https://github.com/kubernetes-sigs/kind/pull/3240/files in favor of setting it via the KubeletConfiguration, which kind was already doing.
There are multiple ways to fix this for CAPD:
Technically it comes down to either:
--fail-swap-on=false
flag on the kubelet (the flag itself is deprecated for usage, I don't know when it gets removed)And there are multiple ways to do that for CAPD, high-level:
Label(s) to be applied
/kind bug
The text was updated successfully, but these errors were encountered: