-
Notifications
You must be signed in to change notification settings - Fork 38.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"kubectl config set" hangs and panics when trying to set user fields #29312
Labels
area/kubectl
priority/important-soon
Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
Comments
@kubernetes/kubectl |
@adohe Would you take a look at this? |
@pwittrock I will take a look today. |
k8s-github-robot
pushed a commit
that referenced
this issue
Aug 6, 2016
…als-auth-providers Automatic merge from submit-queue kubectl config set-crentials: add arguments for auth providers This PR adds `--auth-provider` and `--auth-provider-arg` flags to the `kubectl config set-credentials` sub-command. There's currently no way of interacting with the new auth provider framework added in #23066 through kubectl. You have to render a custom kubeconfig to use them. Additionally `kubectl config set` just sort of craps out when attempting to interact with authentication info objects (#29312). This is a minimal implementation of allowing `kubect config set-credentials` to set fields for client auth providers. cc @cjcullen @kubernetes/kubectl
@adohe Is this still relevant? |
@pwittrock I believe we can close this now, #30007 is merged already. Thanks @ericchiang |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
area/kubectl
priority/important-soon
Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
Trying to set some values in a kubeconfig related to the client auth provider added in #23066.
Here's my current attempt.
The text was updated successfully, but these errors were encountered: