Epic Goal

This EPIC is focusing on merging the current RHDHPAI gitops repos into a single repo, while making easier the process of provisioning further environments (e.g. for demo purposes)

• Include the development environment (team dev instance) and the staging environment (ai rolling demo) under the same gitops repo.
• Align all RHDHPAI environments to use the same format (RHDH Operator + Backstage CR)
• Define patterns between the environments in order to reduce redundancy.
• Create the necessary process that allows us to provision more environments while avoiding the increase of resource demands (e.g. make sure that all RHDH instance are using the same RHOAI or ArgoCD instance).
• Additionally, another goal of the epic is to align the ai-rhdh-installer in the format followed by the unified RHDHPAI gitops repo.

Why is this important?

• Cost-wise: Ensures that we use a single cluster for all of our environments and a specific number of GPU nodes.
• Flexibility-wise: Allows us to be flexible and serve quickly requests for new RHDHPAI demo environments that include a specific feature set.

Scenarios

N/A

Acceptance Criteria (Mandatory)

• CI - MUST be running successfully with tests automated
• Release Technical Enablement - Provide necessary release enablement details and documents.
• The two gitops repos have been migrated to the new common gitops repo.
• Our ROSA cluster contains the applications from the new repo.
• The ai-rhdh-installer is aligned with the new common repo.

Dependencies (internal and external)

1. ...

Previous Work (Optional):

1. …

Open questions::

1. …

Done Checklist

• Acceptance criteria are met
• Non-functional properties of the Feature have been validated (such as performance, resource, UX, security or privacy aspects)
• User Journey automation is delivered
• Support and SRE teams are provided with enough skills to support the feature in production environment