TPT-4221: Enhance security of kubeconfig file permission - #919
Open
yec-akamai wants to merge 2 commits into
Open
TPT-4221: Enhance security of kubeconfig file permission#919yec-akamai wants to merge 2 commits into
yec-akamai wants to merge 2 commits into
Conversation
yec-akamai
added
the
improvement
yec-akamai
requested review from
mawilk90 and
zliang-akamai
and removed request for
a team
August 7, 2026 14:53
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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
Ensure that kubeconfig files are now created via 600 instead of 644. Permissions are set atomically at creation, so contents are never briefly world-readable. Pre-existing files with group/other bits set are tightened to 600 on write. The parent directory is created with mode 700.
✔️ How to Test