You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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}
We will need to pass --cert-dir in the component args: --cert-dir=/var/lib/rancher/k3s/server/tls/{component}
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.
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
The text was updated successfully, but these errors were encountered: