-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
Key Management System - Kubernetes Token Based Auth out of date. #12472
Comments
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in a week if no further activity occurs. Thank you for your contributions. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in a week if no further activity occurs. Thank you for your contributions. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in a week if no further activity occurs. Thank you for your contributions. |
This issue has been automatically closed due to inactivity. Please re-open if this still requires investigation. |
still good to fix this |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in a week if no further activity occurs. Thank you for your contributions. |
The following documentation is out of date with Kubernetes v1.24
https://rook.io/docs/rook/latest/Storage-Configuration/Advanced/key-management-system/#token-based-authentication
The documentation implied that a Secret is generated when a Service Account is created, however, this is no longer true in Kubernetes v1.24: https://www.linkedin.com/pulse/service-account-token-changes-kubernetes-version-124-shafeeque-aslam
Expected Behavior:
The documentation should include how to manually create a secret, or leverage some of the newer design patterns from the latest kubernetes version. Vault documentation here: https://developer.hashicorp.com/vault/docs/auth/kubernetes
The text was updated successfully, but these errors were encountered: