Skip to content

feat: add KubeConfigExecProvider for dynamic cluster credentials#27743

Open
kushwiz wants to merge 1 commit intoargoproj:masterfrom
kushwiz:kushalb/kubeconfig-exec
Open

feat: add KubeConfigExecProvider for dynamic cluster credentials#27743
kushwiz wants to merge 1 commit intoargoproj:masterfrom
kushwiz:kushalb/kubeconfig-exec

Conversation

@kushwiz
Copy link
Copy Markdown

@kushwiz kushwiz commented May 7, 2026

Add support for a new cluster authentication method that executes an external command to produce a full kubeconfig file dynamically. Unlike ExecProviderConfig which only produces credentials, this provider generates an entire kubeconfig (server, CA, auth) that ArgoCD reads to build a REST config.

Key changes:

  • New KubeConfigExecProvider type in ClusterConfig
  • SetConfigProvider option in gitops-engine cluster cache for dynamic config refresh on each sync cycle
  • Unit tests for new functionality

Closes #26729

Checklist:

  • Either (a) I've created an enhancement proposal and discussed it with the community, (b) this is a bug fix, or (c) this does not need to be in the release notes.
  • The title of the PR states what changed and the related issues number (used for the release note).
  • The title of the PR conforms to the Title of the PR
  • I've included "Closes [ISSUE #]" or "Fixes [ISSUE #]" in the description to automatically close the associated issue.
  • I've updated both the CLI and UI to expose my feature, or I plan to submit a second PR with them.
  • Does this PR require documentation updates?
  • I've updated documentation as required by this PR.
  • I have signed off all my commits as required by DCO
  • I have written unit and/or e2e tests for my change. PRs without these are unlikely to be merged.
  • My build is green (troubleshooting builds).
  • My new feature complies with the feature status guidelines.
  • I have added a brief description of why this PR is necessary and/or what this PR solves.
  • Optional. My organization is added to USERS.md.
  • Optional. For bug fixes, I've indicated what older releases this fix should be cherry-picked into (this may or may not happen depending on risk/complexity).

feat: add KubeConfigExecProvider for dynamic cluster credentials
6c071bf 
Add support for a new cluster authentication method that executes an
external command to produce a full kubeconfig file dynamically. Unlike
ExecProviderConfig which only produces credentials, this provider
generates an entire kubeconfig (server, CA, auth) that ArgoCD reads
to build a REST config.

Key changes:
- New KubeConfigExecProvider type in ClusterConfig
- SetConfigProvider option in gitops-engine cluster cache for
  dynamic config refresh on each sync cycle
- Unit tests for new functionality

Closes argoproj#26729

Signed-off-by: Kushal Bhandari <kushalb@fb.com>
@kushwiz kushwiz requested a review from a team as a code owner May 7, 2026 22:51
@bunnyshell
Copy link
Copy Markdown

bunnyshell Bot commented May 7, 2026 •
edited
Loading

🔴 Preview Environment stopped on Bunnyshell

See: Environment Details | Pipeline Logs

Available commands (reply to this comment):

  • 🔵 /bns:start to start the environment
  • 🚀 /bns:deploy to redeploy the environment
  • ❌ /bns:delete to remove the environment

@kushwiz kushwiz mentioned this pull request May 7, 2026
Open
13 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

Enhancement Proposal: KubeConfigExecProvider for Dynamic Cluster Credentials

1 participant

@kushwiz