Please avoid using FCOS 33.20210301.3.1 for new OKD installs
Due to several issues ([1] and [2]) fresh installations using FCOS 33.20210301.3.1 would fail. The fix is coming in Podman 3.1.0.
Due to several issues ([1] and [2]) fresh installations using FCOS 33.20210301.3.1 would fail. The fix is coming in Podman 3.1.0.
It’s possible to completely automate the process of installing OpenShift/OKD on vSphere with User Provisioned Infrastructure by chaining together the various functions of OCT via a wrapper script.
This describes the resources used by OpenShift after performing an installation using the default options for the installer.
This describes the resources used by OpenShift after performing an installation using the default options for the installer.
This describes the resources used by OpenShift after performing an installation using the default options for the installer.
This document outlines how to deploy a single node OKD cluster using virt.
This document lays out the resources used to create my completely-overkill homelab. This cluster provides all the compute and storage I think I'll need for the foreseeable future, and the CPU, RAM, and storage can all be scaled vertically independently of each other. Not that I think I'll need to do that for a while.
This document outlines how to deploy a single node (the real hard way) using UPI OKD cluster on bare metal or virtual machines.
This describes the resources used by OpenShift after performing an installation to make it similar to my homelab setup.