Skip to content
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

Authentication problem when creating new cluster #265

Open
codedge opened this issue Mar 22, 2019 · 3 comments
Open

Authentication problem when creating new cluster #265

codedge opened this issue Mar 22, 2019 · 3 comments

Comments

@codedge
Copy link

codedge commented Mar 22, 2019

Hi,

when I want to create a new cluster with hetzner-kube cluster create --name stmr --ssh-key stmr I get the the following error:

2019/03/22 22:55:08 Creating new cluster

NAME:stmr
MASTERS: 1
WORKERS: 1
ETCD NODES: 0
HA: false
ISOLATED ETCD: false
2019/03/22 22:55:08 creating server 'stmr-master-01'...
2019/03/22 22:55:08 loading server 'stmr-master-01'...
2019/03/22 22:55:08 Created node 'stmr-master-01' with IP xxx.xxx.xxx.xxx
2019/03/22 22:55:09 creating server 'stmr-worker-01'...
2019/03/22 22:55:09 loading server 'stmr-worker-01'...
2019/03/22 22:55:09 Created node 'stmr-worker-01' with IP xxx.xxx.xxx.xxx
stmr-master-01       : ...ting for cloud-init completio    7.7% [--------------]
stmr-worker-01       : ...ting for cloud-init completio   11.8% [--------------]
ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remainssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remainssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain2019/03/22 22:55:41 ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain
$ hetzner-kube ssh-key list
NAME
stmr

I installed hetzner_kube via go get -u github.com/xetys/hetzner-kube on MacOS 10.14.3
I use a normal rsa key, 4096 bit.

Any idea?

@celevra
Copy link

celevra commented Nov 21, 2019

same problem here

if you add the key by hand directly in the hetzner webinterface it works. Problem only exists if you add the key trough hetzner-kube

@alexzimmer96
Copy link
Contributor

The key location is persisted into the ~/.hetzner-kube/config.json as a relative location. Did you maybe run the create-command from another folder then you run the command to add the SSH-Key?

@celevra
Copy link

celevra commented Nov 21, 2019

no

cat .hetzner-kube/config.json | jq .
{
  "active_context_name": "kube",
  "contexts": [
    {
      "token": "xxx",
      "name": "kube"
    }
  ],
  "ssh_keys": [
    {
      "name": "acid@slut",
      "private_key_path": "/root/.ssh/id_rsa",
      "public_key_path": "/root/.ssh/id_rsa.pub"
    }
  ],
  "clusters": []
}

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants