Skip to content
This repository was archived by the owner on Mar 2, 2022. It is now read-only.

Conversation

@craigtracey
Copy link
Contributor

It is unclear why the kubelet no longer set this parameter by default,
but it is necessary for installs and upgrades. Adding it to the
/etc/kubelet/default file.

Signed-off-by: Craig Tracey craigtracey@gmail.com

It is unclear why the kubelet no longer set this parameter by default,
but it is necessary for installs and upgrades. Adding it to the
/etc/kubelet/default file.

Signed-off-by: Craig Tracey <craigtracey@gmail.com>
Copy link
Contributor

@alexbrand alexbrand left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. Do we need to cherry-pick forward?

@alexbrand
Copy link
Contributor

I wonder if there is a deeper problem when upgrading from v1.10 to v1.11:
kubernetes/kubeadm#1418

Based on that issue, it looks like when doing an upgrade the /var/lib/kubelet/kubeadm-flags.env config file is only rendered on control plane nodes, but not on worker nodes. I am guessing we could be missing other important kubelet config?

@alexbrand
Copy link
Contributor

Chatted with @craigtracey and we believe this is good to merge.

@scottslowe
Copy link
Contributor

Can we close this PR, since 1.11.x is no longer a supported/maintained release? Or have we confirmed that we need this change in newer branches/releases?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants