In a recent conversation, an OpenShift 4 administrator used the phrase “Because SSH is disabled in these AMIs…”. But that’s not the right way to think about things! With OpenShift 4, the goal is that all aspects of the operating system are controlled by the cluster and one can configure them in a uniform fashion “day 1” and “day 2” via
Let’s unpack this a bit more. First, with Fedora/RHEL CoreOS, we have a high degree of uniformity for the base OS across platforms – for example, we avoid including any platform specific agents, and we also try really hard to have the OS work the same way across platforms because while we have different disk images per platform (unavoidable), we have exactly one in-place update stream that applies across all of them.
The state of having SSH enabled or not does not vary across platforms or “AMIs” – it works exactly the same on a bare metal OpenShift 4 install as it does in AWS.
Second, we use Ignition and the machine config operator as a uniform way to configure things – so if you want to enable or disable SSH or configure keys – it again works exactly the same across platforms.
Specifically, if you provide SSH public keys to the installer configuration that basically ends up generating an Ignition config that applies on firstboot – the “AMI” here isn’t relevant.
This part of “configure the OS via Ignition” is common to Fedora and RHEL CoreOS. With OpenShift 4 we also have integrated “day 2” changes, so one can e.g. update SSH keys “day 2”.
To emphasize this, as an OpenShift 4 administrator, you manage your ssh keys via
oc/kubectl – the same way you manage other aspects of the cluster, and the same way across platforms.