OpenShift Single-Node Cluster Setup & Optimization Guide for Enterprise Linux Engineers (2026)

Red Hat OpenShift is the industry standard enterprise Kubernetes platform. While production multi-master clusters require substantial infrastructure, Single Node OpenShift (SNO) and Red Hat OpenShift Local (formerly CodeReady Containers / CRC) enable system administrators, DevOps engineers, and cloud architects to run a complete OpenShift cluster on a single workstation or server host.

This guide covers architectural concepts, hardware requirements, deployment steps, storage provisioning, and day-2 operations for OpenShift on Enterprise Linux.

1. Single-Node OpenShift (SNO) vs OpenShift Local (CRC)

Before deployment, select the operational model that matches your workflow requirements:

• Red Hat OpenShift Local (CRC): Tailored for local developer desktops. Runs inside a managed hypervisor VM (KVM/QEMU) with automated setup via the crc CLI tool. Ideal for ephemeral labs and testing.
• Single Node OpenShift (SNO): Combines control plane and worker node responsibilities into a single bare-metal or virtualized RHEL CoreOS (RHCOS) instance. Perfect for edge deployments and dedicated server environments.

2. Hardware & Host Prerequisites

3. Preparing the Linux Host Environment

Ensure NetworkManager and libvirt virtualization service stacks are running clean on your host server before initiating the installation process.

Step 1: Install KVM & Virtualization Packages

# On RHEL/AlmaLinux/Rocky Linux
sudo dnf groupinstall -y "Virtualization Headless"
sudo dnf install -y libvirt qemu-kvm virt-install network-manager-passthrough

# Start and enable libvirtd daemon
sudo systemctl enable --now libvirtd

Step 2: Enable Nested Virtualization

If running OpenShift inside a hypervisor VM (such as Proxmox or ESXi), verify nested virtualization support is enabled for Intel/AMD CPUs:

# Check Intel
cat /sys/module/kvm_intel/parameters/nested

# Check AMD
cat /sys/module/kvm_amd/parameters/nested

If output returns Y or 1, nested virtualization is active.

4. Step-by-Step Deployment of OpenShift Local (CRC)

Step 1: Download and Extract CRC Binary

cd /tmp
wget https://developers.redhat.com/content-gateway/rest/mirror/pub/openshift-v4/clients/crc/latest/crc-linux-amd64.tar.xz
tar -xvf crc-linux-amd64.tar.xz
sudo cp crc-linux-*-amd64/crc /usr/local/bin/
crc version

Step 2: Configure CRC Resource Limits

Set custom CPU and memory parameters tailored for your host specs:

crc config set memory 28672
crc config set cpus 6
crc config set disk-size 80
crc config set consent-telemetry no

Step 3: Setup and Start OpenShift Local

# Prepare virtualization backend & networking
crc setup

# Start OpenShift cluster (pass Red Hat pull secret when prompted)
crc start --pull-secret-file=/path/to/pull-secret.txt

5. Accessing the OpenShift Cluster and OC CLI

Once deployment finishes, export your Kubeconfig environment variables to interact with the API server via oc and kubectl commands.

# Export Kubeconfig paths
eval $(crc oc-env)

# Login as Developer or Kubeadmin user
oc login -u kubeadmin -p $(crc console --credentials | grep kubeadmin | awk '{print $NF}') https://api.crc.testing:6443

# Check node health and pod status
oc get nodes
oc get clusteroperators

6. Key Takeaways

• Single-Node OpenShift is a game changer for building enterprise cloud-native skills without needing costly multi-server infrastructure.
• Podman and CRI-O serve as the underlying container runtimes, ensuring full alignment with OCI standards.
• Always ensure adequate disk throughput (NVMe recommended) as etcd requires low disk write latency.