Value Statement

 Enhance ClusterCurator controller to support setting the .spec.channel field on HostedCluster CRs. Modifications are needed to support hosted cluster channel setting feature in the ACM/MCE console.

Definition of Done for Engineering Story Owner (Checklist)

• ClusterCurator can read channel selection from Job (requesting HostedCluster channel update)
• ClusterCurator updates HostedCluster CR's .spec.channel field

Technical Notes:

• Hypershift requires release image pull specs for updates
• Unlike standalone OCP, cannot simply set desired version string
• ClusterCurator will need to translate channel/version selections to proper digest-based pull specs
• Coordinate with Console team on UI input model
• Setting channel tells CVO where to look for update advice
• Must use digest-based pull spec (e.g., quay.io/openshift-release-dev/ocp-release@sha256:...)
• Tag-based pull specs work but bypass security checks
• Consider how to source the correct digest for selected versions

Development Complete

• The code is complete.
• Functionality is working.
• Any required downstream Docker file changes are made.

Tests Automated

• [ ] Unit/function tests have been automated and incorporated into the
  build.
• [ ] 100% automated unit/function test coverage for new or changed APIs.

Secure Design

• [ ] Security has been assessed and incorporated into your threat model.

Multidisciplinary Teams Readiness

• [ ] Create an informative documentation issue using the Customer

Portal Doc template that you can access from [The Playbook](

https://docs.google.com/document/d/1YTqpZRH54Bnn4WJ2nZmjaCoiRtqmrc2w6DdQxe_yLZ8/edit#heading=h.9fvyr2rdriby),

and ensure doc acceptance criteria is met.

• Call out this sentence as it's own action:

• [ ] Link the development issue to the doc issue.

Support Readiness

• [ ] The must-gather script has been updated.