Hi Parag,
with IPI You should pass the SSH key as one of the parameters in install-config.yaml file. If You have not done so, You can add (or change) the SSH keys as day-2 operation with use of MachineConfig - details here: https://access.redhat.com/solutions/3868301
That said, You do not need to connect via SSH to do administrative tasks like increasing disk size. It can be done using 'oc debug node/<node_name>' command which gives You host level access.
Regards,
------------------------------
Witold Wierzchowski
Solution Architect
Cohesive Poland
------------------------------
Original Message:
Sent: Mon November 11, 2024 06:43 AM
From: Parag Agnihotri
Subject: SSH to AWS SNO created using mascli provision-aws option
We followed the link Installation of MAS Manage on Red Hat OpenShift (SNO) on AWS Using the MAS DevOps Ansible Collection
to install Single Node Openshift on AWS using docker image of mascli. The installation was successfull but we would like to now ssh into the Single Node machine for doing linux based activity like increasing the disk size of root disk (Increasing the EBS volume of the EC2 instance does not increase the Node disk size).
Since the method used was IPI, there was no step of generating SSH Keys on the bastion machine and running the oc command to install the cluster.
Can anyone help in letting us know how to SSH in the SNO machine?
------------------------------
Parag Agnihotri
------------------------------