Skip to content
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

CASMPET-7224: remove unnecessary checking of some kubelet certs #5369

Merged
merged 1 commit into from
Sep 13, 2024

Conversation

bo-quan
Copy link
Contributor

@bo-quan bo-quan commented Sep 12, 2024

Description

When checking expiration dates of kubelet certs, not all kubelet certs need to be current. Once kubelet certificate is rotated, /var/lib/kubelet/pki/kubelet.crt is no longer used; instead the symbolic link /var/lib/kubelet/pki/kubelet-client-current.pem is used and points to the latest rotated certificate. Only cert in kubelet-client-current.pem file needs to be current. This PR fixes the doc issue.

Checklist

  • If I added any command snippets, the steps they belong to follow the prompt conventions (see example).
  • If I added a new directory, I also updated .github/CODEOWNERS with the corresponding team in Cray-HPE.
  • My commits or Pull-Request Title contain my JIRA information, or I do not have a JIRA.

@bo-quan
Copy link
Contributor Author

bo-quan commented Sep 12, 2024

/backport release/1.5 release/1.4

Copy link
Contributor

Backporting into branch release/1.5 was successful. New PR: #5370

Copy link
Contributor

Backporting into branch release/1.4 was successful. New PR: #5371

@rustydb
Copy link
Contributor

rustydb commented Sep 13, 2024

Spellcheck is complaining about lines not touched in this PR, ignoring for now as Bo is out.

@rustydb rustydb merged commit 001142d into release/1.6 Sep 13, 2024
7 of 8 checks passed
@rustydb rustydb deleted the CASMPET-7224 branch September 13, 2024 18:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants