You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
copy script to /opt/backup/certs/ssh (public only) id_rsa.pub
copy kubernetes certs to /opt/backup/certs/kubernetes
then on Ingress instance in k8s-install.sh script copy from s3 back to /opt/backup/certs/ssh and /opt/backup/certs/kubernetes folders only
append (not replace) public ssh key from /opt/backup/certs/ssh/id_rsa.pub to /users/ubuntu/.ssh/authorized_keys (make sure permissions and ownership stays the same)
you should now be able to continue with kubernetes node to join master as well as have ability to connect to node from Core.
The text was updated successfully, but these errors were encountered:
would be appropriate to move current /opt/backup/certs to /opt/backup/certs/ssl but that would require change of ALL references. and there are quite a few
We will use S3 private bucket for Core/Cluster cert distribution.
copy script to /opt/backup/certs/ssh (public only) id_rsa.pub
copy kubernetes certs to /opt/backup/certs/kubernetes
then on Ingress instance in k8s-install.sh script copy from s3 back to /opt/backup/certs/ssh and /opt/backup/certs/kubernetes folders only
append (not replace) public ssh key from /opt/backup/certs/ssh/id_rsa.pub to /users/ubuntu/.ssh/authorized_keys (make sure permissions and ownership stays the same)
you should now be able to continue with kubernetes node to join master as well as have ability to connect to node from Core.
The text was updated successfully, but these errors were encountered: