To ensure the highest levels of security, we recommend that remote SSH access not be enabled on the VM instances. SSH type of access is not required for any operations performed by administrators. The Controller provides a zero trust, remote diagnostics and control channel that can be leveraged securely as long as
- The VM is operational and
- The VM has network connectivity to the Controller.
Access VM Instance¶
We recommend that customers that require this type of access use “Console” access from within vSphere. This approach ensures that access to the VM is only possible by “approved and authenticated” vSphere administrators.
Use the username “rafay_admin” for this type of access.
Illustrative screenshot below for access to a VM Instance via vSphere Console.
Although remote access to the VM instance via SSH is not required, if you would like enable this, follow the steps described below.
This will require you to operate at a degraded security level
The following default access credentials can be used for SSH access to the underlying OS backing the k8s cluster.
Username: rafay_admin Password: Admin$321
Access vSphere Console¶
Login as rafay_admin via console of VM in vSphere Console
Switch to Root¶
sudo su -
Modify the file "/etc/ssh/sshd_config" to enable password based authentication over ssh.
Update "PasswordAuthentication" from "no" to "yes"
Enable SSH in the VM¶
Enable ssh in the VM by typing the following command.
systemctl enable ssh
systemctl start ssh