Skip to content
This repository has been archived by the owner on Jul 25, 2022. It is now read-only.

gardenctl can not support aws format kubeconfig #217

Closed
knightXun opened this issue Jul 7, 2020 · 2 comments · Fixed by #221
Closed

gardenctl can not support aws format kubeconfig #217

knightXun opened this issue Jul 7, 2020 · 2 comments · Fixed by #221

Comments

@knightXun
Copy link

knightXun commented Jul 7, 2020 •
edited
Loading

it's seems gardenctl will read some content from kubeconfig, and judge the format whether is illeage.I see some code of gardenctl and compare this with my aws format kubeconfig, finding gardenctl can not support aws kubeconfig very well. Please notice this.
@neo-liang-sap
Copy link
Contributor

neo-liang-sap commented Jul 7, 2020 •
edited
Loading

gardenctl can't support some kind of kubeconfig e.g. containing use with command line content.
say if your kubeconfig user part contains aws-iam-authenticator command line to generate user info, this could not be consumed by gardenctl

thanks

@knightXun
Copy link
Author

@neo-liang-sap thanks.

@neo-liang-sap neo-liang-sap mentioned this issue Jul 14, 2020
Merged
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

remove exec and auth provider check to utilize kubeconfig with oidc enabled neo-liang-sap/gardenctl
2 participants
@knightXun @neo-liang-sap