Uploaded image for project: 'RHOS Request for Features'
  1. RHOS Request for Features
  2. RHOSRFE-286

GitOps-Driven RHOSO deployment

    • Icon: Feature Request Feature Request
    • Resolution: Duplicate
    • Icon: Undefined Undefined
    • None
    • None
    • False
    • False
    • Hide

      None

      Show
      None

      Feature Request Overview
      My Customer aims to use GitOps workflow for RHOSO deployment and scale up activities.
      My customer is using Distributed Zones architecture, with 3 AZs, 3 Cells (one Cell by AZ). Later, he's aiming to customize his deployment with one DB and one RabbitMQ for each RHOSO service.

      Business justification
      Improve the consistency and automation of RHOSO deployments across multiple environments such as DEV, PRE-PROD, PROD1, PROD2, .. PROD N using a GitOps strategy.
      This reduces operational costs and minimise errors by automating the deployment process of all RHOSO clusters.
       
      Goals

      • GitOps-Driven RHOSO deployment
      • GitOps-Driven RHOSO Scale up

      Done - Acceptance Criteria:
      Validated GitOps architecture/pattern for RHOSO deployments.

      (Optional) Point of contact
      TAM

              pnavarro@redhat.com Pedro Navarro Perez
              smsallem@redhat.com Soumaya Msallem
              Gil Rosenberg
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: