Backport: [user-authn] Add ServiceAccount to templates #13221
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Add separate ServiceAccount to
basic-auth-proxy
templateWhy do we need it, and what problem does it solve?
According to CIS 5.1.5, default service account should not be used for Kubernetes API access
Why do we need it in the patch release (if we do)?
In v1.69 basic-auth-proxy fails to start, this changes will fix it.
Checklist
Changelog entries