-
Epic
-
Resolution: Done
-
Major
-
None
-
GCP: Support RHCOS Image coming from a custom source
-
BU Product Work
-
False
-
False
-
Green
-
Done
-
OCPSTRAT-482 - Support custom RHCOS image location for GCP and Azure
-
OCPSTRAT-482Support custom RHCOS image location for GCP and Azure
-
0% To Do, 0% In Progress, 100% Done
-
Undefined
-
Epic Goal
- As a customer, I need to make sure that the RHCOS image I leverage is coming from a trusted source.
Why is this important?
- For customer who have a very restricted security policies imposed by their InfoSec teams they need to be able to manually specify a custom location for the RHCOS image to use for the Cluster Nodes.
Scenarios
- As a customer, I want to specify a custom location for the RHCOS image to be used for the cluster Nodes
Acceptance Criteria
A user is able to specify a custom location in the Installer manifest for the RHCOS image to be used for bootstrap and cluster Nodes. This is the similar approach we support already for AWS with the compute.platform.aws.amiID option
Previous Work (Optional):
https://issues.redhat.com/browse/CORS-1103
Done Checklist
- CI - CI is running, tests are automated and merged.
- Release Enablement <link to Feature Enablement Presentation>
- DEV - Upstream code and tests merged: <link to meaningful PR or GitHub Issue>
- DEV - Upstream documentation merged: <link to meaningful PR or GitHub Issue>
- DEV - Downstream build attached to advisory: <link to errata>
- QE - Test plans in Polarion: <link or reference to Polarion>
- QE - Automated tests merged: <link or reference to automated tests>
- DOC - Downstream documentation merged: <link to meaningful PR>