Allow setting automountServiceAccountToken #1284
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.
What does this PR do?
By default, kubernetes enables "automountServiceAccountToken" for all pods, see https://kubernetes.io/docs/tasks/configure-pod-container/configure-service-account/#opt-out-of-api-credential-automounting.
This poses a security risk, as pods might get kube-api permissions unintentionally.
More specifically, this fails security compliance tests:
https://learn.microsoft.com/en-us/azure/governance/policy/samples/built-in-policies
https://www.azadvertizer.net/azpolicyadvertizer/kubernetes_block-automount-token.html
Solution - Disable "automountServiceAccountToken", create projected volume for the token, and mount it on relevant containers
Submitter checklist
./charts/jenkins/Chart.yaml
../charts/jenkins/CHANGELOG.md
..github/helm-docs.sh
from the project root.Special notes for your reviewer
This does not effect default behavior, though if someone is looking to comply with security requirements and disable this, they must also manually mount the serviceAccount token, with the following values.yaml: