-
Notifications
You must be signed in to change notification settings - Fork 513
Update custom CAs on existing nodes #10923
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
Update custom CAs on existing nodes #10923
Conversation
d951edc
to
804edb1
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.
/lgtm
LGTM label has been added. Git tree hash: b730137b722868f4e5293172302876bd51da3003
|
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: rfranzke 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 |
This reverts commit b88242d.
This reverts commit b88242d.
How to categorize this PR?
/area ops-productivity
/kind enhancement
What this PR does / why we need it:
At the moment custom CAs are applied when the node is created only. Existing nodes are not updated.
This PR changes this behavior and allows updating custom CAs on existing nodes. It is possible to restart containerd without restarting all containers (ref) which was not the case for docker. As Gardener does not support Docker anymore, this change is possible now.
When custom CAs change
containerd
andkubelet
services are restarted on the node.Other services affected by CA changes like
gardener-node-agent
(ref) andvalitail
(ref) already include the CA bundle in their configuration or as own file, so they are restarting already.Which issue(s) this PR fixes:
Fixes #10040
Special notes for your reviewer:
Release note: