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
Default secret with token for service account is not the default behavior #37393
Comments
/kind bug |
/triage accepted /language en The one-line fix you suggested seems reasonable, @srm09 |
Hi. I'm not sure I'd have time to provide guidance specifically on this issue. Could you ask in Slack - see https://slack.k8s.io/ for an invitation - in the #sig-docs channel? I hope if you ask questions there, someone is willing to help you learn how to contribute here. |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
@srm09 This is addressed in the newer documentation. Can you please recheck and close the issue? |
/remove-lifecycle stale |
With 1.24, the
LegacyServiceAccountTokenNoAutoGeneration
feature gate is beta and enabled by default. This stops the auto generation of secrets containing service account token for every ServiceAccount.Bu the docs on the site refer to the previous assumption that a token gets created by default for all service accounts.
Problematic line:
A controller loop ensures a Secret with an API token exists for each ServiceAccount.
The text was updated successfully, but these errors were encountered: