-
Notifications
You must be signed in to change notification settings - Fork 238
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
Rotating the admin kubeconfig after 10 years #1933
Comments
I've created a story within our board https://issues.redhat.com/browse/HIVE-2084. I labeled the issue so that we will discuss at our next grooming and we will update this issue once we have. Thanks! |
Bookmarking this KCS article with procedure for generating a new admin kubeconfig https://access.redhat.com/solutions/5286371. It is possible that this procedure could be automated by a controller. |
Issues go stale after 90d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle stale |
Stale issues rot after 30d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle rotten |
Rotten issues close after 30d of inactivity. Reopen the issue by commenting /close |
@openshift-bot: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
The admin kubeconfigs generated for any new cluster at install time is valid for 10 years. Ref: https://access.redhat.com/solutions/4845381.
How will hive rotate this certificate after 10 years?
The text was updated successfully, but these errors were encountered: