OS Customizations

The upgrade from Oracle CNE Release 1 to Release 2 uses the Bring Your Own (BYO) provider. The image used for the BYO provider is based on OSTree. The steps in this guide use two methods of upgrade, either installing the OS image on an system's existing disk (using the Anaconda and Kickstart installation options of Oracle Linux), or swapping a virtual disk with one that contains the OS image.

The Oracle CNE Release 2 OS image doesn't provide the option to install or configure the OS after it's deployed. The OS image is immutable and can't be changed after it's installed. Any customizations to the OS must be done in the image used for the installation of Release 2. Any updates to the OS must be done using a new OSTree based image, which is how OS updates are performed.

If you have any customized OS requirements on the systems in the Oracle CNE Release 1 cluster, you need to identify those before you begin the upgrade. For example, if you have any software packages and OS configuration that's in addition to the standard requirements in the Release 1 deployment.

If any customizations are required, you might have the option to set these in a Release 2 cluster configuration file. If configuration file options are available for the customization, ensure you add these to a cluster configuration file before you upgrade. For information on the available cluster file configuration options, see Oracle Cloud Native Environment: Kubernetes Clusters.

If customization settings aren't available in a cluster configuration file option, you might need to use Oracle Container Host for Kubernetes Image Builder to build a custom image. For information on building a custom image, see Oracle Cloud Native Environment: Oracle Container Host for Kubernetes Image Builder.