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.

Sign up for GitHub

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

Jump to bottom

Fix a TODO for kubeconfig rotation #122

Merged

mogliang merged 1 commit into k3s-io:main from nasusoba:kubeconfig2

May 29, 2024

Contributor

nasusoba commented May 23, 2024 •

edited

Loading

Fix a TODO for rotating kubeconfig secret if it is close to expiring
- When created, kubeconfig secret will be effective for a year. If kubeconfig secret will expired in 180 days, it will get rotated
Address RestConfig creation failure as RemoteClusterConnectionError (same as CAPI)

I have manually verified the cert could be rotated and the rotated secret could still be used to connect to the workload cluster.


          add kubeconfig rotation

6a5a222

Signed-off-by: nasusoba <[email protected]>

mogliang approved these changes

View reviewed changes

mogliang merged commit a3067a7 into k3s-io:main

5 checks passed

nasusoba deleted the kubeconfig2 branch

May 29, 2024 02:52

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet