Goals:

To apply a team-specific configuration on top of the generic agent architecture to specifically define our teams cluster(s) and Gitlab pipeline:

• Agent DOES expect particular output, stages, and job to exist in Workflow validation projects
• Agent CAN trigger and monitor available pipeline stages/jobs in Workflow validation project
• Agent CAN identify the gaps between the current state of an OpenShift AI cluster and the expected state

Acceptance Criteria:
Once customized, the Ikari DevOps agent:

• expects team-specific details
• can provide the user with the ability to troubleshoot a given cluster
• can trigger specific pipeline jobs to deploy and destroy an fresh single-node OpenShift AI cluster (via mapt)