-
Notifications
You must be signed in to change notification settings - Fork 195
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
EKS ? yes #266
Comments
As reported in #266 , let's add EKS as "works".
How to authenticate with EKS? it ask for token, while Lens can do without asking for a token. |
The inability to easily use kubeconfig w/EKS AWS_PROFILE is a showstopper for us (unlike Octant, Lens, OpenLens, Aptakube, etc.) |
So whats the solution for this ?? how do I connect to the clusters which are listed in my kube config file ? |
bump |
is there anybody who was able to access EKS cluster using the token generated from aws eks get-token |
EKS: not yet When the aws CLI adds a cluster to my kubeconfig, it adds an eks get-token command exec to the config. Headlamp reads the kubeconfig and lists the cluster. However, when I try to connect then headlamp asks me for a token. This is odd because the command to fetch a token is right there in the kubeconfig. Furthermore, since the eks get-token expires relatively quickly, there's no use in me entering a token manually. (Furthermore, Lens and Octant work as I expect.) |
FTR, in the case of @joebowbeer this has to do with running when kubeconfig is set to use the exec plugin for getting the token from |
@joaquimrocha indeed we are also having the same issues as reported by @joebowbeer on the desktop version when connecting to AWS/EKS clusters. Not only that, but we are also unable to connect to Azure/AKS clusters. Kubectl, Lens and vscode work well. |
Hi @joaocc , what version and flavor of Headlamp are you using? (Mac/Linux/Windows) |
Desktop-wise I am having issues with macOS and latest headlam. |
works like a charm on 2 clusters i tried.
using Version 0.3.0 (0.3.0) :)
much faster than Lens
The text was updated successfully, but these errors were encountered: