privatecoder
privatecoder
Does this need to happen during deployment? I add additional labels and taints aftrewards.
@vitobotta if you add this you can also go ahead and add the same for taints, i.e. ``` worker_node_pools: - name: sql-engine-small instance_type: cpx21 instance_count: 3 labels: purpose: sql-engine size:...
Did you guys check (SSH'ing to one of the nodes) if anything from the stuff in the yaml (additional packages) and / or if k3s gets installed?
I just deployed a single master, single worker test-cluster using 0.6.3 on macOS 12.3.1 on a M1 machine successfully. However I did have to add my SSH private key to...
Well I did just test the tool on my end to see if I could help here, but it creates the cluster flawlessly. However I encountered the issue above when...
I am not however adding it to the keychain fixes the error ``` # add keys to keychain # ssh-add --apple-use-keychain ~/.ssh/[your-private-key] (>=12.x) # ssh-add -K ~/.ssh/[your-private-key] (
@vitobotta is it possible that the Ubuntu image used by Hetzner to setup the machine has now changed to use ed25519 and therefore also your Docker images etc are affected...
I will. Let me restart and see if the error still occours and then try the gem. One sec..
Restarting and removing commenting out my ssh-config brings back the issue: ``` #Host * # UseKeychain yes # AddKeysToAgent yes # IdentityFile ~/.ssh/id_rsa ``` Let's see what the gem does..
@vitobotta removed hetzner-k3s via brew uninstall however it is stll working. Do you know where the bin installed by brew is located?