These OpenShift and Kubernetes manifest files support the installation of Red Hat OpenShift clusters on Oracle Cloud Infrastructure. The Butane files used to generate the OpenShift MachineConfigs are also included.
View usage during installation
| File | Description | When to Use |
|---|---|---|
| 01-oci-ccm.yml | Cluster resources for OCI Cloud Controller Manager (CCM). | Always ✅ |
| 01-oci-csi.yml | Cluster resources for OCI Cloud Storage Interface (CSI). See STORAGE.md | Always ✅ |
| 01-oci-driver-configs.yml | Configuration Secrets for CCM and CSI drivers. ❗Contains placeholder values that need to be replaced before use. | Always ✅ |
| 02-machineconfig-ccm.yml | MachineConfig that fetches the provider (OCI) id for kubelet from the OCI metadata of the instance. | Always ✅ |
| 02-machineconfig-csi.yml | MachineConfig that enables the iscsid.service to run. | Always ✅ |
| 03-machineconfig-consistent-device-path.yml | MachineConfig that ensures consistent device paths when attaching paravirtualized volumes to instances. | Always ✅ |
| 04-cluster-network.yml | Cluster resource that configures the default Network's internalMasqueradeSubnet xto 169.254.64.0/18 to avoid collisions with iSCSI boot volumes. | Required when using Bare Metal instances with OpenShift versions >= 4.17 |
| 05-oci-eval-user-data.yml | MachineConfig that evaluates and runs userdata scripts stored in the metadata of instances. | Required when using Bare Metal instances |
Most of our terraform-stacks have an output called dynamic_custom_manifest. This output contains all required manifests, concatenated and pre-formatted with the configuration values for CCM and CSI. This output can be copied and used to create a single manifest file which can then be uploaded during the cluster installation process.
There is also a non-dynamic condensed-manifest.yml which contains all manifests (for easier upload), but still requires the sections for CCM and CSI configuration values to be replaced by the RMS job output oci_ccm_config, or manually formatted with OCI resource OCID's from your existing cluster infrastructure. These sections have been marked with a TODO so they can be easily located and replaced. See oci-cloud-controller-manager example for more information.
Each folder in oci-ccm-csi-drivers contains manifest files corresponding to a release version of the OCI CCM and CSI drivers. These files can be applied to an existing cluster to update the driver resources on the cluster to a specific version.
If you have oc installed and your KUBECONFIG is pointing at your cluster, you can use the command
make update-drivers
to update the drivers on your cluster to the latest version, or run the command with a specific OCI_DRIVER_VERSION to downgrade/upgrade as necessary e.g.
make update-drivers OCI_DRIVER_VERSION=v1.25.0