-
Notifications
You must be signed in to change notification settings - Fork 125
Description
THIS ISSUE IS MOVED TO openshift/enhancements#201
First, be sure you're familiar with os updates.
Currently, we have no default mechanism to update the bootimages once a cluster is installed. For example, as of 4.1.4 today, the way things work is that the installer pins RHCOS, and when a cluster is installed in e.g. AWS, the installer injects the AMI into the machinesets in openshift-machine-api. Nothing thereafter updates it. And because we haven't updated the pinned RHCOS for 4.1.X today every OpenShift install uses the 4.1.0 RHCOS bootimages. (More on that below)
Now, see:
openshift/origin#21998
for a PR which tries to embed this metadata into the release image. From there, we could imagine having e.g. the cluster API use it to update the machinesets.
However, the "fully managed AWS" environment is the easy one. We have to consider manual bare metal PXE setups as well as private OpenStack clouds. For private clouds like OpenStack (as well as AWS Outpost for that matter) one could imagine that we ship all of the images in a container, or perhaps a "pristine" disk image in a container, and also the tooling (cosa gf-oemid) to stamp it, as well as an operator to pull those bootimages and upload them to glance or private AWS.
The bare metal PXE case is unmanaged; we are probably just going to have to suffer and try to point people doing this towards managed metal.
As of today though, we will have to support upgrading OpenShift from the 4.1.0 bootimages for...quite a while.