fix: migrate ExecCredential API from v1beta1 to v1#641
Merged
Conversation
client.authentication.k8s.io/v1beta1 has been deprecated and removed in recent Kubernetes versions. Update to v1 which has an identical response structure.
kralicky
approved these changes
Mar 9, 2026
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
2 participants
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.
Summary
The Kubernetes
client.authentication.k8s.io/v1beta1API version used forExecCredentialhas been deprecated and removed in recent Kubernetes versions. This updates the exec credential plugin to useclient.authentication.k8s.io/v1, which has an identical response structure for the status fields used by this plugin.Related issues
N/A
Checklist
improvement/bug/ etc)