fix: set automountServiceAccountToken to false when default service account is used #172
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 of the change
Sets
automountServiceAccountToken: false
when the default service account is used.Benefits
This would lead to a more secure setup.
Possible drawbacks
None that come to my mind
Additional information
We follow the CIS Kubernetes Benchmark recommendations for a secure Kubernetes cluster setup.
As per point 5.1.5 Ensure that default service accounts are not actively used:
The default service account should not be used to ensure that rights granted to applications can be more easily audited and reviewed.
The suggested remediation is:
Create explicit service accounts wherever a Kubernetes workload requires specific access to the Kubernetes API server. Modify the configuration of each default service account to include this value:
Checklist
Chart.yaml
according to semver.