4.3.25

User Story

As an OpenShift cluster admin/installer
I want the registry to be Removed on Baremetal installations
So that I can provision other storage providers
And later enable the image registry with the desired storage

Acceptance Criteria

• On baremetal IPI installs (platform = BareMetal):
  • Registry management state is Removed
  • Registry reports itself as Available with a reason that makes it clear the registry has been removed (ex: Reason=Removed) - likely already done
• Day 2 configuration works as expected (should work today):
  • Cluster admin is able to configure storage for the registry (ex: EmptyDir for CI testing).
  • Registry can be transitioned to Managed.
  • Once Managed, registry is available and operating normally.
  • Verify that the internal registry hostname has been published on image.config.openshift.io/cluster
• Telemetetry and alerting
  • Report the registry has been removed (reason code `Removed` in the cluster operator status conditions)
  • Warning alert if the registry has been removed.

Launch Checklist

Dependencies identified
Blockers noted and expected delivery timelines set
Design is implementable
Acceptance criteria agreed upon
Story estimated

Notes

Enhancement proposal: https://github.com/openshift/enhancements/pull/45

Dependencies

• CI needs an e2e-baremetal job (or equivalent)

Questions

• Do different baremetal platforms need to be distinguished? Ex: what RHHI needs vs. RHV. For registry no, but perhaps other components will need this.
• Telemetry/alerting - we may get Management state in telemeter. We can/should report the Available reason as Removed.
• Baremetal testing - Need to make sure that our baremetal test suites are updated and can be invoked via an e2e-baremetal job

• https://github.com/openshift/cluster-image-registry-operator/pull/392

• https://github.com/openshift/cluster-ingress-operator/pull/300

User Story

As an OpenShift user on Power and Z
I want the Samples operator to not provision templates on Power and Z
So that customers do not have images and templates that do not work on Power and Z

Acceptance Criteria

• Samples operator installs vetted content from openshift/library appropriate for the cluster architecture
• Samples operator does not install Jenkins imagestreams and templates on Power or Z (even though a Jenkins image may be in the release payload).
• Samples operator behaves normally if no imagestreams/templates are available for the cluster architecture (reports itself Available=true, Progressing=false, Degraded=false).

Launch Checklist

Dependencies identified
Blockers noted and expected delivery timelines set
Design is implementable
Acceptance criteria agreed upon
Story estimated

Notes

Assumptions

• Clusters will be homogeneous - mixed x86 and Power/Z nodes are not in scope.

Dependencies

• Jenkins will not be available on Power and Z in the 4.3 timeframe. Decision has been made to put the x86 image in the release payload (it will break if somehow ran).
• Platform architecture may need to be available on the cluster so we can bootstrap with the correct arch.
  • If not available, use GOARCH variable.

• https://github.com/openshift/cluster-samples-operator/pull/187

• https://github.com/openshift/cluster-network-operator/pull/376