-
Feature
-
Resolution: Unresolved
-
Critical
-
None
-
None
-
None
-
Strategic Product Work
-
False
-
-
False
-
OCPSTRAT-1750Continuous Integration Testing of ARO Installation
-
0% To Do, 100% In Progress, 0% Done
-
0
Goal
Stop using the openshift/installer-aro repo during installation of ARO cluster. installer-aro is a fork of openshift/installer with carried patches. Currently it is vendored into openshift/installer-aro-wrapper in place of the upstream installer.
Benefit Hypothesis
Maintaining this fork requires considerable resources from the ARO team, and results in delays of offering new OCP releases through ARO. Removing the fork will eliminate the work involved in keeping it up to date from this process.
Resources
https://docs.google.com/document/d/1xBdl2rrVv0EX5qwhYhEQiCLb86r5Df6q0AZT27fhlf8/edit?usp=sharing
It appears that the only work required to complete this is to move the additional assets that installer-aro adds for the purpose of adding data to the ignition files. These changes can be directly added to the ignition after it is generated by the wrapper. This is the same thing that would be accomplished by OCPSTRAT-732, but that ticket involves adding a Hive API to do this in a generic way.
Responsibilities
The OCP Installer team will contribute code changes to installer-aro-wrapper necessary to eliminate the fork. The ARO team will review and test changes.
Success Criteria
The fork repo is no longer vendored in installer-aro-wrapper.
Results
Add results here once the Initiative is started. Recommend discussions & updates once per quarter in bullets.
- relates to
-
OCPSTRAT-742 Add support to disable SNAT for outbound traffic on Azure
- Backlog
-
OCPSTRAT-506 ARO Managed Identity
- Closed
-
OCPSTRAT-716 Mixed public/private exposure for OpenShift API and OpenShift Ingress on Azure
- Closed
- links to