Installing on a single node OpenShift (SNO) cluster

IBM Cloud Pak® for Integration supports installations on single node OpenShift (SNO).

For more information on how to install Red Hat® OpenShift® Container Platform on a single node, see Installing OpenShift on a single node.

SNO offers a fully-functional Red Hat OpenShift Container Platform installation with a reduced footprint, where control and worker node functionality is combined on a single node.

Implications of using SNO

The implications of running on a single node include:

  • More limited options for workload availability. For example, the redundancy in multi-node clusters that enables workloads to failover to other workers is not present. Rolling upgrades for pods and multi-replica deployments can mitigate this limitation.

  • Any OpenShift configuration change that requires the node to reboot or drain, such as OpenShift upgrades, will cause downtime in any deployed instance.

Advantages of using SNO

Using SNO clusters can be an advantage in these scenarios:

  • A resource-constrained environment. For more information on installing instances with minimal footprint, see Compute resources for development environments.

  • Edge sites where Red Hat OpenShift Container Platform is required and node failure can be mitigated.

For more information, see Meet single node OpenShift: Our newest small OpenShift footprint for edge architectures.