OpenShift Update Service for OKD

[disposab1e]

Cause we're running OKD in an disconnected environment we're very interested in using the OpenShift Update Service as described here.

Everything works fine but the missing bits are the cincinnati graph data for OKD. For OpenShift it is available here.

Any chance to find a repo like this for OKD too?

[vrutkovs]

OKD doesn't use OSUS instance, but uses Cincinnati protocol to control upgrade graph.

OSUS allows us to modify graph using channels and edge blocks via cincinnati-graph-data. OKD is using a simplified version of it - github.com/openshift/release-controller, which can build the graph dynamically based on Prow upgrade jobs (if the test passes the upgrade edge is added). Release controller channels are defined in release repo, but has no concept of blocked edges or promotion windows.

However you can still use OSUS and OSUS operator to update a disconnected fleet of OKD instances - but you'd have to come up with settings and cincinnati-graph-data repo yourself.

[disposab1e]

@vrutkovs Thx for your detailed reply! I added a channel stable-4 to cincinnati graph data repo with following content:

but you'd have to come up with settings and cincinnati-graph-data repo yourself

/channels/stable-4.yaml

name: stable-4
versions:
- 4.8.0-0.okd-2021-10-24-061736
- 4.8.0-0.okd-2021-11-14-052418

/blocked-edges/4.8.0-0.okd-2021-10-24-061736.yaml

to: 4.8.0-0.okd-2021-10-24-061736
from: 4\.7\..*

/blocked-edges/4.8.0-0.okd-2021-11-14-052418.yaml

to: 4.8.0-0.okd-2021-11-14-052418
from: 4\.7\..*

I don't want to waste your time. Just a quick question... is this enough? yes/no

Of course additionally I did everything documented here.

[vrutkovs]

Looks sufficient to me

[disposab1e]

/channels/okd-4.yaml

name: okd-4
versions:
- 4.8.0-0.okd-2021-10-24-061736
- 4.8.0-0.okd-2021-11-14-052418

Everything looks good... but the next version is not available... @vrutkovs do you have a hint what can be missing?

[disposab1e]

@vrutkovs do you have a hint what is missing?