-
Notifications
You must be signed in to change notification settings - Fork 7
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
login-add-eks-cluster-support #1102
Conversation
Pinged bigmac as the owners of the login command |
if r.loginOptions.isWCClientCert { | ||
return r.handleWCClientCert(ctx) | ||
if r.loginOptions.isWC { | ||
err := r.handleWCKubeconfig(ctx) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Same here, the function being called is specifically for handling client certs on a workload cluster. (We are planning to move this to a different command so it'll be helpful to keep the name)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
the function for handling clientcert is still there it just moved later to avoid code duplication
https://github.com/giantswarm/kubectl-gs/pull/1102/files#diff-1f160945410f9311805f9b1ff5284e4cbb59cdd8934057db5bd7b3e40049979fR199-R271
Added few comments as we agreed in the call. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thank you ❤️
towards giantswarm/roadmap#2609
add
opsctl login
support for EKS WCas EKS only supports kubeconfigs with aws cli IAM auth, its necessary to have active and working AWS credentials in order to use the kubeconfig, there is no proper workaround