Goal
As an OSD customer, I want a managed OpenShift GitOps service on OpenShift Dedicated clusters so that I can adopt GitOps and Argo CD as a service without having to learn the operational skills for managing OpenShift GitOps. When customer purchases an OSD cluster, then they will have a seamlessed managed OpenShift platform with the OpenShift GitOps add-on for use by customer.
Acceptance Criteria
- Requirements for OpenShift GitOps becoming an add-on on OSD is understood and documented.
Documents
Planning Docs from jgwest:
- Introduction to OSD add-ons (targeted for members of the GitOps team that are new to OSD)
- Requirements that we will need to fulfill, based on OSD add-on checklists
- Initial proposed plan to meet OSD addon requirements
Google Drive folder containing all of the above: https://drive.google.com/drive/u/0/folders/1_52e6r6w9eEg7eEEAeAJDV-7WPXNJm0f
- relates to
-
GITOPS-1016 GitOps use on OSD/ROSA through OperatorHub
- Closed