-
Epic
-
Resolution: Done
-
Normal
-
None
-
None
-
None
-
Get CAPZ image from the OCP release image
-
Strategic Product Work
-
False
-
None
-
False
-
Not Selected
-
To Do
-
OCPSTRAT-981 - Implement Lifecycle & Image Management for NodePools
-
OCPSTRAT-981Implement Lifecycle & Image Management for NodePools
-
Hypershift Sprint 244, Hypershift Sprint 245
-
0
-
0
-
0
User Story:
As a user of HyperShift, I want the cluster API Azure (CAPZ) image to come from the OCP release image rather than being hardcoded in the HyperShift code so that I can always use the latest CAPZ image related to the OCP release image.
Acceptance Criteria:
The CAPZ image comes from the OCP release image.
Out of Scope:
N/A
Engineering Details:
- The CAPZ image only comes from the OCP release image if:
- the CAPZ image is not set through an environment variable
- the CAPZ image is not set through an annotation on the HostedCluster CR
This requires/does not require a design proposal.
This requires/does not require a feature gate.