Skip to content

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

Merged

Conversation

oliver-goetz
Copy link
Member

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 and kubelet services are restarted on the node.
Other services affected by CA changes like gardener-node-agent (ref) and valitail (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:

Custom CAs are updated on existing nodes too.

@gardener-prow gardener-prow bot added area/ops-productivity Operator productivity related (how to improve operations) kind/enhancement Enhancement, improvement, extension cla: yes Indicates the PR's author has signed the cla-assistant.io CLA. labels Nov 26, 2024
@gardener-prow gardener-prow bot added the size/M Denotes a PR that changes 30-99 lines, ignoring generated files. label Nov 26, 2024
@oliver-goetz oliver-goetz force-pushed the enh/update-ca-on-existing-nodes branch from d951edc to 804edb1 Compare November 26, 2024 13:14
Copy link
Member

@marc1404 marc1404 left a comment

Choose a reason for hiding this comment

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

/lgtm

@gardener-prow gardener-prow bot added the lgtm Indicates that a PR is ready to be merged. label Nov 27, 2024
Copy link
Contributor

gardener-prow bot commented Nov 27, 2024

LGTM label has been added.

Git tree hash: b730137b722868f4e5293172302876bd51da3003

@rfranzke
Copy link
Member

rfranzke commented Dec 9, 2024

/approve

Copy link
Contributor

gardener-prow bot commented Dec 9, 2024

[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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@gardener-prow gardener-prow bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Dec 9, 2024
@gardener-prow gardener-prow bot merged commit b88242d into gardener:master Dec 9, 2024
18 checks passed
@oliver-goetz oliver-goetz deleted the enh/update-ca-on-existing-nodes branch December 10, 2024 11:41
nschad added a commit to stackitcloud/gardener that referenced this pull request Feb 3, 2025
ske-prow bot pushed a commit to stackitcloud/gardener that referenced this pull request Feb 3, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. area/ops-productivity Operator productivity related (how to improve operations) cla: yes Indicates the PR's author has signed the cla-assistant.io CLA. kind/enhancement Enhancement, improvement, extension lgtm Indicates that a PR is ready to be merged. size/M Denotes a PR that changes 30-99 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Install Custom CA certs also for existing nodes
3 participants