Story (Required)

As a user of RHDH trying to install one of the ai software tempaltes I want to be able to choose a remote cluster to deploy the template's resources.

Apart from the UI side I want to have the documentation in place so I can figure out easily how I can add a new remote cluster on my argoCD installation.

Background (Required)

The current issue is scoping on the UI side of the template and the creation of the parameters/values passed to the gitops side in order to create the corresponding resources.

The new values could be included similarly to what we have done for the bearer authentication of existing model servers support.

On the docs side, we should add information on the pre-requisites that the remote cluster needs based on the argoCD docs https://argo-cd.readthedocs.io/en/stable/operator-manual/declarative-setup/#clusters and how someone can initialize a namespace on their remote cluster prior of installing a software tamplate

Out of scope

Only the updates on the ai-lab-template side is included in the scope of this issue.

Approach (Required)

In regards to the UI we need to communicate the new fields with the UI team to see what fits best our case. One approach that we followed during the investigation phase was:

Dependencies

This is the last issue after all updates are made to the gitops-side and the investigation for the kubernetes resources is finished.

Acceptance Criteria (Required)

• New fields are added in all templates
• All gitops updates are imported
• All templates run correctly with a remote cluster involved
• Documentation/instructions are added for the support of remote clusters in the argoCD instance and on how a user can initialize a remote namespace

documentation updates (design docs, release notes etc)
demo needed
SOP required
education module update (Filled by RHDHPAI team only)
R&D label required (Filled by RHDHPAI team only)

Done Checklist

Code is completed, reviewed, documented and checked in
Unit and integration test automation have been delivered and running cleanly in continuous integration/staging/canary environment
Continuous Delivery pipeline(s) is able to proceed with new code included
Customer facing documentation, API docs, design docs etc. are produced/updated, reviewed and published
Acceptance criteria are met
If the Grafana dashboard is updated, ensure the corresponding SOP is updated as well