Feature Request Overview 

Customers upgrading from Red Hat OpenStack Platform (RHOSP) 17.1 to Red Hat OpenStack Services on OpenShift (RHOSO) 18 currently follow a written procedure for the Adoption Mechanism. However, this process is manual and lacks GitOps integration. The goal of this feature request is to enhance the upgrade experience by providing documented examples of how to automate the Adoption Mechanism using GitOps practices with ArgoCD and Kustomize, improving consistency, traceability, and operational efficiency.

Business justification (mandatory - Complete while in New status)
How would this feature benefit the customer?

• Provides a repeatable and automated upgrade process aligned with GitOps principles.

• Reduces the potential for human error during control plane and data plane adoption.

• Improves visibility and auditability of the upgrade workflow via Git history.

• Aligns with customers’ existing GitOps pipelines and CI/CD best practices.

• Accelerates time-to-value for customers adopting RHOSO, lowering operational overhead.

Functional requirements (mandatory - Complete while in New status){_}

• Provide official documentation with a GitOps-compatible version of the RHOSP to RHOSO adoption steps.
• Include example ArgoCD Application manifests and kustomization.yaml files covering:
  • Adoption preparation
  • Control plane CR deployments
  • Dataplane service updates
  • Reboot orchestration
• Offer guidance for structuring a Git repository to manage the RHOSO upgrade lifecycle via GitOps.
• Document rollback strategies using GitOps tooling.
• Include validation/test playbooks for pre- and post-adoption checks (via ArgoCD hooks or Jobs).

Describe the customer impact{}

This feature would significantly improve the day-2 operational experience of RHOSO adoption by enabling automation, auditability, and integration into existing GitOps workflows. It supports scaling and repeatability across environments and aligns with how cloud-native customers manage modern infrastructure updates.

(Optional) Point of contact

• Provide any additional points of contact for this feature request, such as an account executive, SA, or TAM: 
•  

(Optional) Additional links

Click More > Link to add any links to issues, such as an outcome, that are related to this feature request.