Skip to content
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

teleport-cluster: set automountServiceAccountToken to false on ServiceAccounts when using newer Kubernetes distributions #47680

Merged
merged 1 commit into from
Oct 18, 2024

Conversation

webvictim
Copy link
Contributor

@webvictim webvictim commented Oct 17, 2024

Security best practices encourage the use of projected ServiceAccount credentials where possible.

This is not a breaking change (or indeed much of a change at all), as Teleport already makes use of projected credentials when on newer distributions. This is essentially setting a value to satisfy a security linter.

changelog: Alter ServiceAccounts in the teleport-cluster Helm chart to automatically disable mounting of service account tokens on newer Kubernetes distributions, helping satisfy security linters.

Fixes #47594

…eAccounts when using newer Kubernetes distributions
@webvictim webvictim enabled auto-merge October 18, 2024 00:07
@webvictim webvictim added this pull request to the merge queue Oct 18, 2024
Merged via the queue into master with commit d001054 Oct 18, 2024
43 checks passed
@webvictim webvictim deleted the gus/helm/serviceaccount-projected-if-supported branch October 18, 2024 11:26
@public-teleport-github-review-bot

@webvictim See the table below for backport results.

Branch Result
branch/v14 Create PR
branch/v15 Create PR
branch/v16 Create PR

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Support automountServiceAccountToken in teleport-cluster helm charts
3 participants