Kubernetes & OpenShift Overview
Kubernetes and OpenShift are an additional STRATUM deployment model. Bring up the controller first, validate it, then add compute and storage roles deliberately.
Deployment model
Kubernetes/OpenShift schedules the STRATUM controller and optional worker roles, but it does not remove STRATUM host requirements. KVM, TUN, host networking/device access, persistent storage, and worker enrollment still have to be satisfied by the selected nodes.
Order of operations
Install the controller alone first. Confirm the pod, persistent volume, logs, and web endpoint. Only after the controller is healthy should you create the worker-enrollment Secret and add compute or storage values layers.
Values layers
Use the supplied controller values as the base. Add the worker values layer for compute, then the storage values layer when storage participation is required. A controller-plus-storage deployment can omit the compute worker values layer when that is the intended topology.
The outcome you should see
You can distinguish the controller, compute-worker, and storage-worker layers and know that controller-only validation comes first.