Uploaded image for project: 'Red Hat Internal Developer Platform'
  1. Red Hat Internal Developer Platform
  2. RHIDP-10724

Create GitOps, Pipelines & ArgoCD Default Installation Helm Chart

    • Icon: Task Task
    • Resolution: Done
    • Icon: Critical Critical
    • None
    • None
    • None
    • HAS Sprint 2269

      Task Description (Required)

       

      _<Task description> _

       

      After the conclusion of https://issues.redhat.com/browse/DEVHAS-735 we verified the steps required to manually setup GitOps and ArgoCD alongside Vanilla RHDH. The scope of this issue is setting up the Helm Chart / scripts necessary to create the GitOps Operator, ArgoCD instance, and Pipelines Operator with default values. Default values in this case mean they are simply installed and not configured as configuration will occur in a separate issue. RHTAP currently has a Helm Chart they use for setup that we can reference. 

       

      The following will need to be accomplished as part of this issue:

      1. Create a new repo in the AI org on GitHub that will be the home of this chart
      2. Create Helm Chart for default installation of GitOps Operator, Pipeline Operator and ArgoCD
        1. Create GitOps Operator subscription
        2. Create Pipeline Operator subscription
        3. Create ArgoCD instance

       

      Notes related to the prior investigation can be found here:

      https://docs.google.com/document/d/1zGNh8RwKbKFjeueci1wd4bQslTJ9EzhAucSArWbpmCQ/edit?usp=sharing

      https://docs.google.com/document/d/1d5gnTV38eyJ9IeP2ay65SO2FN0ldzjTOrLv0lgvi5pY/edit?usp=sharing

       

       

      If this requires Change Management, complete sections below: 

      Change Request 

       

      <Select which item is being changed>

       

      [ ]  Add New Tokens

      [ ]  Rotate Tokens

      [ ]  Remove Tokens

      [ ] Others: (specify)

       

        Environment

      <Select which environment the change is being made on.  If both, open a separate issue so changes are tracked in each environment>

       

      [ ]  Stage OR

      [ ]  Prod

       

        Backout Plan

      <State what steps are needed to roll back in case something goes wrong>

       

        Downtime

      <Is there any downtime for these changes?  If so, for how long>

       

        Risk Level

      <How risky is this change?>

       

        Testing

      <How are changes verified?>

       

        Communication

      <How are service owners or consumers notified of these changes?>

              rh-ee-jdubrick Jordan Dubrick
              rh-ee-jdubrick Jordan Dubrick
              RHIDP - AI
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: