Closed mburke5678 closed 8 months ago
Need to wait until #2 is complete, so that content can be the basis of the docs
There are two ways to install SNO:
The Agent-based Installer approach will work when this has been merged. The OCP-documented approach works in 4.15 and will work in 4.14 when this has been merged.
FWIW, I'm looking forward to this because I have a server in my homelab waiting for OKD.
Good news:
~: oc get nodes
NAME STATUS ROLES AGE VERSION
okd-sno-test Ready control-plane,master,worker 46m v1.27.9+e36e183
~: oc get clusterversion
NAME VERSION AVAILABLE PROGRESSING SINCE STATUS
version 4.14.0-0.okd-2024-01-26-175629 True False 25m Cluster version is 4.14.0-0.okd-2024-01-26-175629
Now just need to document it.
Hello @mburke5678,
I started to document the required steps and got a question: as I saw in a previous commit you had, it's possible to mark if a part is only for OCP or if that's for OKD. Is it necessary to add ifndef::openshift-origin[]
in case the given section is only for OCP?
My feeling is that it's required, but I'd like to be sure.
Thanks @peterroth this is closed by ther merge of openshift/openshift-docs#71809
https://github.com/openshift/openshift-docs/issues/51152
The OKD end user docs have instructions for Installing "OpenShift on a single node" that is OCP-specific.
It needs to be significantly rewritten:
The files are to be hidden on OKD docs until we can make these changes.
Assemblies: installing/installing_sno/install-sno-preparing-to-install-sno.adoc installing/installing_sno/install-sno-installing-sno.adoc