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
Transition service account controller clients to TokenRequest API #71275
Comments
/assign |
/cc |
/cc @yliaog |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
/reopen Some aspects remain. |
@enj: Reopened 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. |
/remove-lifecycle stale |
The controller manager handles controller clients via the
ControllerClientBuilder
interface. The core implementation isSAControllerClientBuilder
(seek8s.io/kubernetes/pkg/controller/client_builder.go
). To get a client for a specific service account, it ensures that the service account exists, and then waits for the token controller to create a secret that contains the service account's token. While the long term desire may be to remove the token controller, we can work towards that goal by moving these clients to theTokenRequest
API.Action items:
SAControllerClientBuilder
should check if theTokenRequest
API is available and use it, otherwise it should fallback to the current behavior of using secret based tokens/sig auth
/sig api-machinery
@kubernetes/sig-auth-feature-requests
xref: #70679
The text was updated successfully, but these errors were encountered: