Skip to content

Generate and manage certificates for kube-scheduler and kube-controller-manager #12172

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

Open
manuelbuil opened this issue Apr 17, 2025 · 1 comment

Comments

@manuelbuil
Copy link
Contributor

Is your feature request related to a problem? Please describe.

We are currently not generating the self-signed certificates of kube-scheduler and kube-controller-manager which makes it impossible to rotate them either by using the CLI or by rebooting the nodes

Describe the solution you'd like

K3s having control over kube-scheduler and kube-controller-manager certificates

Describe alternatives you've considered

Additional context

@brandond
Copy link
Member

brandond commented Apr 17, 2025

  1. We need to generate additional certs+keys in the same paths as the components use when generating self-signed certs:
    /var/lib/rancher/k3s/server/tls/{component}/{component}.{crt,key}
  2. We will need to pass --cert-dir in the component args:
    --cert-dir=/var/lib/rancher/k3s/server/tls/{component}
  3. The cert will need to be signed by the K3s ServerCA and have the full ServerCA chain in it, as Rancher is using the cert as the CA bundle because it expects the cert to be self-signed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: New
Development

No branches or pull requests

2 participants