Describes custom images in OSTree archive format to create Kubernetes nodes in Bring Your Own clusters.

Custom installations of OCK are done using the Anaconda and Kickstart automatic installation options of Oracle Linux. Anaconda requires OSTree content to be available in a particular format to install onto the root file system of the target host (an OSTree archive served over HTTP). The OCK container image used for updates isn't in this format. To use the content with Anaconda, it must be converted to an archive and made available using an HTTP server.

Images can be created using the ocne image create command with the --type ostree option. The resulting container image is stored in the Open Container Initiative archive format and can be imported to the local cache or pushed to a container registry. Building the container image pulls a base image from within the Kubernetes cluster (this is either the existing cluster set using a kubeconfig file, or an ephemeral cluster that's started for this purpose).

By default, the image is created for the architecture of the system where the command is run. Images can be created for other architectures using the --arch option.

Typically, OSTree archive images are copied to a container registry. You can copy the image to any target that works with the Open Container Initiative transports and formats. See containers-transports(5) for available options.