• Icon: Task Task
    • Resolution: Done
    • Icon: Critical Critical
    • None
    • None
    • None
    • DEVAI Sprint 3262, DEVAI Sprint 3263, DEVAI Sprint 3264

      Task Description (Required)

       

      _<Task description> _

       

      After completion of https://issues.redhat.com/browse/DEVHAS-752 and https://issues.redhat.com/browse/DEVHAS-753 there will be Helm Charts responsible for creating default setup instances of Vanilla RHDH, GitOps Operators, ArgoCD, and Pipeline Operators. The scope of this issue is to create a configuration script that takes input from the user regarding all of the necessary information to setup RHDH so that it can work with all the operators and argocd to enable the use of software templates.

      You can reference the Slack conversation about this configuration here: https://redhat-internal.slack.com/archives/C03A062K00K/p1723049352449039

       

      You can reference RHTAPs setup to get an understanding of the information required from the user: https://github.com/redhat-appstudio/rhtap-installer/blob/main/bin/make.sh#L256-#L380 and https://github.com/redhat-appstudio/rhtap-installer/blob/main/chart/values.yaml

      In addition to the script that sets and creates the necessary configmaps, secrets, and updates the RHDH information there should be another script that performs the entire lifecycle of steps. This script would first install the operators and rhdh via their helm charts and then call the configuration script.

       

      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?>

              mvaldron Michael Valdron
              rh-ee-jdubrick Jordan Dubrick
              RHIDP - AI
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: