kubernetic
kubernetic copied to clipboard
harbur
Unable to use EKS generated kubeconfig
For whatever reason, within Kubernetic if I am using a Kube config generated by aws eks update-kubeconfig it always errors out with "Cannot Login: Get "https://B00AB7128C9986D06A6B978E0F18835A.yl4.us-east-1.eks.amazonaws.com/version?timeout=32s": getting credentials: exec: exit status 254".
This is with Kubernetic v2.13.0
Hi,
A common issue is that aws must be under the PATH so that kubernetic can exec the command. You can configure the PATH on preferences section.
can you try again with PATH setup properly? Note that the PATH of your shell is not delegated to the desktop app.
Already have the path setting set to ‘/usr/local/bin’, that was a separate issue
From: Dimitris Kapanidis [email protected] Reply-To: harbur/kubernetic [email protected] Date: Friday, October 16, 2020 at 11:55 AM To: harbur/kubernetic [email protected] Cc: "Avery, Reuben (NBCUniversal)" [email protected], Author [email protected] Subject: [EXTERNAL] Re: [harbur/kubernetic] Unable to use EKS generated kubeconfig (#256)
Hi,
A common issue is that aws must be under the PATH so that kubernetic can exec the command. You can configure the PATH on preferences section.
can you try again with PATH setup properly? Note that the PATH of your shell is not delegated to the desktop app.
[Screenshot 2020-10-16 at 17 53 04]https://urldefense.com/v3/__https:/user-images.githubusercontent.com/367397/96280665-88f45a80-0fd8-11eb-89a7-8d35cdd5f986.png__;!!PIZeeW5wscynRQ!666-lyMqbdLB25C8E6K-o_R5PEUWym1g_6FqgTDSELG8sIPwS7HNiSx38YCwKWQjkQ$
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHubhttps://urldefense.com/v3/__https:/github.com/harbur/kubernetic/issues/256*issuecomment-710133633__;Iw!!PIZeeW5wscynRQ!666-lyMqbdLB25C8E6K-o_R5PEUWym1g_6FqgTDSELG8sIPwS7HNiSx38YBWxwiQ5w$, or unsubscribehttps://urldefense.com/v3/__https:/github.com/notifications/unsubscribe-auth/AAAVOW3HOULYULODWXCQKPLSLBUG5ANCNFSM4STPNXEQ__;!!PIZeeW5wscynRQ!666-lyMqbdLB25C8E6K-o_R5PEUWym1g_6FqgTDSELG8sIPwS7HNiSx38YCi0vXucA$.
This may be connected with #283
I noticed that not every kube config is parsed correctly, in my case it was plus sign but there may be more special chars that stops kubernetic. Maybe instead of that kubectl config get-contexts should be in use?
