Story

OKD has a FeatureSet of its own and the current FeatureSets for the dualstream feature gate (OSStreams) does not include the OKD FeatureSet (see: https://github.com/openshift/api/blob/9a67b6dd449db74432fed86fc4ab3922775cbaa4/features/features.go#L919-L925). This creates a behavior gap between OKD and OCP. Since these types of gaps usually result in a future maintenance burden by forcing OKD to be handled differently, we would prefer to align OKD with OCP.

The exception will be that OKD uses a single OSImageStream pointing to the available tags in the payload ImageStream. With this in place, removing the FeatureGate conditions for the General Availability (GA) release will be straightforward.

This card is not about supporting dual-streams in OKD, we won't support OKD, but about handling OKD just as we do OCP but with one single hardcoded stream.

Acceptance Criteria

• OKD uses OSImageStreams.

• OKD reports an OSImageStream with a single stream pointing to the available tags in the payload ImageStream.

• OKD conditionals are removed where the code checks for the existence of the OSImageStream Custom Resource (CR).

Implementation Details

• In addition to the work within the MCO repo, a PR will be needed to openshift/api to add the OKD FeatureSet to the enableIn() set for OSStreams.