Repository navigation
Add application-controlled security policies for kubeconfig exec plugins - #1930
Conversation
There was a problem hiding this comment.
Copilot wasn't able to review any files in this pull request. Check if the Files changed in this pull request are included in default exclusions.
|
@copilot can you add documentation that this is intended for defense in depth and is not a hard security boundary, loading a kubeconfig from an untrusted source is an inherently dangerous activity and should be handled as part of an overall security model, not relying exclusively on this capability. |
Added the README clarification in commit |
There was a problem hiding this comment.
🔵 Needs a closer look
The environment filter still permits BASH_FUNC_ overrides, allowing a kubeconfig to inject code into an allowlisted Bash credential script despite blocking BASH_ENV.
No open issues 🎉
2 resolved since last review
Review effort: Balanced
a1499ea to
58ff291
Compare
|
/lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: brendandburns, Copilot The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |


Untrusted kubeconfigs can launch arbitrary local processes through exec credential plugins. This adds application-controlled authorization without requiring callers to parse and inspect kubeconfig themselves.
AllowAll(default),DenyAll, andAllowlistpolicies across configuration builders, including Classic and AOT. Existing API signatures remain available.ExecCredentialPluginDeniedException; kubeconfig cannot override the application policy.