The dashboard for droplets tells me the monitoring should be upgraded on the droplet used as Kubernetes node. I would like to upload my ssh key to that droplet in order to login and upgrade. I understand this is not possible with the current Droplet so I went to create another one. However, I couldn’t find how to upload or configure the ssh key for an additional Kubernetes node. Anything I have been missing or are the Kubernetes nodes managed by DigitialOcean and thus prohibiting us to log on those droplets ?
This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.
Click below to sign up and get $200 of credit to try our products over 60 days!
If you’re using our Kubernetes-as-a-service product, these nodes are not accessible via SSH and the monitoring agent is not intended to function there right now. It’s a good point about the message, and something to look at as we continue to iterate on this product.
To access via ssh kubernetes droplets, you needs configure firewall to accept connections in 22 port. You can access firewall settings in droplet overview, on Networking item.
You can reset the password for the droplet, open SSH in the cluster’s firewall, and then SSH in with the new password. It would be nice if there was a way to pre-configure authorized keys for new nodes, though. SSHing into a cluster node is often necessary for debugging.