Hello,

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 ?

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.

×
4 answers

Greetings!

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.

Jarland

  • Thank you for the answer.
    It is quite unfortunate if the monitoring agent isn’t supposed to work. It is pretty nice to get an idea about the droplet usage and should help scaling the cluster.

I would like to access Digital Ocean Kubernetes-as-a-service nodes over ssh and looks like it still not possible. I can ssh to nodes from inside the cluster but outside.

As I mount Persistent Volumes on host OS sometimes its nice to have an option of direct connection to host OS in oder to manage files.

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.

  • Second that.

    So here is a quick hack I have used to SSH without requiring to reset the root password.

    Create a Pod and mount the /root/.ssh directory using hostPath volume mount. Then echo the pub file contents into authorized_keys, exit the shell and delete the pod.

    You can now SSH to the instance. :)

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.

Submit an Answer