OpenShift Guide
Day 9 — Edge & Hybrid Cloud
MicroShift, SNO, ACM fleet management, ZTP, and disconnected deployments
Edge Architecture Patterns
Edge deployments push workloads physically closer to data sources — manufacturing floors, retail locations, telecommunications sites, and federal forward operating bases. OpenShift spans the continuum from a full cluster to a single-node to a minimal microcontroller-grade footprint with MicroShift.
Core Data Center
Full multi-node OpenShift. Central management hub. Runs ACM, Quay mirror registry, and GitOps controllers. Pushes policies and images to the edge.
Near Edge (SNO)
Single Node OpenShift. One physical or virtual machine runs all control plane and worker roles. Suitable for remote offices, branch sites, and ruggedized servers.
Far Edge (MicroShift)
Minimal Kubernetes runtime (< 200 MB) optimized for constrained hardware — 2 CPU, 4 GB RAM. Targets OT/IoT gateways, retail kiosks, and vehicle-mounted compute.
Single Node OpenShift (SNO) Install Config
apiVersion: v1
baseDomain: example.com
metadata:
name: edge-site-01
compute:
- name: worker
replicas: 0 # SNO: no separate worker nodes
controlPlane:
name: master
replicas: 1 # Single control plane node
platform:
baremetal:
rootDeviceHints:
deviceName: /dev/sda
networking:
networkType: OVNKubernetes
clusterNetwork:
- cidr: 10.128.0.0/14
hostPrefix: 23
serviceNetwork:
- 172.30.0.0/16
platform:
baremetal:
apiVIP: "192.168.1.10" # VIP for kube-apiserver
ingressVIP: "192.168.1.11" # VIP for ingress router
hosts:
- name: edge-node-01
role: master
bmc:
address: ipmi://192.168.1.5
credentialsName: edge-node-bmc-creds
bootMACAddress: "AA:BB:CC:DD:EE:FF"
rootDeviceHints:
deviceName: /dev/sda
pullSecret: '<pull-secret>'
sshKey: '<ssh-public-key>'ZTP (Zero Touch Provisioning)