Update OCP versions on Assisted Installer Stage Slide: https://hackmd.io/@vrutkovs/demo-assisted-service-stage openshift-edge-bot is periodically creates PRs to update assisted-service metadata after parsing Cincinnati endpoint to find new stable updates Example: https://github.com/openshift/assisted-service/pull/3699 Stage instance Stage instance needs to be updated separately.

Source code All software starts at the source code. In OKD's case there are multiple repos under the https://github.com/openshift organization. Lets pick one for example - https://github.com/openshift/origin-branding. Its a simple image, consisting of: manifests/0000_10_origin-branding_configmap.yaml - a configmap telling console to use OKD branding and linking to OKD documentation Dockerfile - instructions for CI how to build that image Note io.openshift.release.operator=true label - that tells OKD's version operator to manage this manifest and reconcile it if changes happen. All changes are built, tested and promoted by our CI, which is Prow. Note the green checkmark near the commit banner, it has a post-submit job:

Fetch expected machineconfig: oc get mc/$(oc get mcp/master -o=jsonpath='{.spec.configuration.name}') -o yaml > mc.yaml Run oc debug node/ip-10-0-130-23.us-east-2.compute.internal and keep it open. In a parallel tab copy MC to the debug container: oc -n openshift-machine-config-operator cp mc.yaml ip-10-0-130-23us-east-2computeinternal-debug:/tmp

Agenda: Release keys - https://github.com/openshift/okd/issues/138 + https://github.com/openshift/cluster-update-keys/pull/16 requires release-controller redeployment Release-controller channels tweaking might be a bug