-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Prompt for Username and Password when running "kubectl get all" #164
Comments
@gmflau - i'm guessing you weren't prompted for a username/password when you ran Could you confirm what version you are using? ( Also, can you confirm kubectl is using your eksctl context? If you run this command |
It did not prompt for username/password when running "eksctl create cluster" command. The output from the command was as follows: $ eksctl version $ kubectl config current-context But when I ran $ kubectl get all, I got the following prompt: |
@gmflau - thanks for sending that through. It sounds like you may have an old version of kubectl version |
That line indicates that there is certainly something odd with You need version 1.10.x, the latest is 1.10.7. |
I will upgrade my kubectl to 1.10.x or higher and give it a try.
…On Tue, Aug 21, 2018 at 3:43 AM, Ilya Dmitrichenko ***@***.*** > wrote:
2018-08-15T12:38:14-07:00 [✖] parsing kubectl version string "0.0.0": Version string empty
That line indicates that there is certainly something odd with kubectl.
Is it an alias or do you have some kind of wrapper?
You need version 1.10.x, the latest is 1.10.7.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#164 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AKPuaUW8UD6jDS6LpCx1wsZ0hMV-329_ks5uS-RPgaJpZM4V-uRz>
.
|
@gmflau did you manage to upgrade and re-test? can we close the issue? |
@gmflau - did upgrading kubectl help with this issue? |
Yes. You can close the issue now.
…On Wed, Sep 5, 2018 at 1:17 AM Richard Case ***@***.***> wrote:
@gmflau <https://github.com/gmflau> - did upgrading kubectl help with
this issue?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#164 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AKPuaZ8lwN3BHfJJZBFraR_fFbnKPSFdks5uX4iYgaJpZM4V-uRz>
.
|
Thanks @gmflau. Closing. |
I experienced this issue today too. Leaving these commands here for reference for anyone else who has kubectl installed both via Homebrew and Docker for Mac.
In my case,
I'd been hanging on an old build of DfM edge as Kubernetes support is somewhat unstable when upgrading. I'm trying the latest DfM edge build now. I'm not sure about the best way to handle having 2 different local Kube versions like this but as a temp fix for now, I've overwritten the alias that currently points to DfM kubectl.
I wonder if I should restrict my client version to 1.10.x to match what's available on EKS. Anyone have thoughts on this? |
I have my Homebrew installed under By the way, I use stable Docker for Mac (18.06.0-ce-mac70), and it worked just fine. I recall having to go through multiple resets/reinstalls doing upgrades on unstable channel, but I believe most of those issues got fixed. In any case, the stable version comes with Generally speaking to your question of managing Perhaps, we could improve the homebrew package to let user know of the caveat with Docker for Mac and Homebrew both using |
Thanks, I'll give the stable channel a shot again. Do you think it makes sense to add a note about this in the docs (README.md)? I'm happy to send a PR if so. |
Yes, please propose what you think would be helpful, please open a PR and
we take it from there :)
…On Tue, 11 Sep 2018, 5:11 pm Taylor D. Edmiston, ***@***.***> wrote:
Thanks, I'll give the stable channel a shot again.
Do you think it makes sense to add a note about this in the docs
(README.md) for this? I'm happy to send a PR if so.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#164 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAPWSy7KKoZYZqRzKZgTyaSRIt8Q7BjRks5uZ-C-gaJpZM4V-uRz>
.
|
i had the same issue, it was provided because of a bad kubectl cluster context, make sure that kubeconfig point to ~/.kube/config in your bashrc then verfiy your context in ~/.kube/config file |
I had similar issue today ..
The loading order follows these rules:
Available Commands: Usage: Use "kubectl --help" for more information about a given command. |
Hi.
|
I used the following command to create my EKS cluster:
% eksctl create cluster --name=eks-c5-xlarge-5 --nodes=5 --node-type=c5.xlarge
Then I was prompted to enter Username and Password when trying to access the cluster by $ kubectl get all. I have no idea what my Username and Password are for the cluster.
The text was updated successfully, but these errors were encountered: