Rename template variable from OPENSHIFT to RHOAI (#139)

Author: dgrove-oss

setup.tmpl/CLUSTER-SETUP.md.tmpl

@@ -1,6 +1,6 @@
 # Cluster Setup
 
-{{ if .OPENSHIFT -}}
+{{ if .RHOAI -}}
 The cluster setup installs Red Hat OpenShift AI and Coscheduler, configures Kueue,
 cluster roles, and priority classes.
 
@@ -27,7 +27,7 @@ Create `default-priority`, `high-priority`, and `low-priority` priority classes:
 
 MLBatch utilizes Kubernetes Scheduler Plugins to ensure gang scheduling of
 multi-Pod workloads and to pack `Pods` onto `Nodes` to reduce GPU fragmentation.
-{{ if not .OPENSHIFT -}}
+{{ if not .RHOAI -}}
 Two options are described below: Coscheduler and Sakkara. You should pick and install one of them
 as a secondary scheduler for your cluster.
 {{- end }}
@@ -45,7 +45,7 @@ Patch Coscheduler pod priorities:
 {{ .KUBECTL }} patch deployment -n scheduler-plugins --type=json --patch-file setup.{{ .VERSION }}/coscheduler-priority-patch.yaml scheduler-plugins-scheduler
 ```
 
-{{ if not .OPENSHIFT -}}
+{{ if not .RHOAI -}}
 ### Sakkara
 
 [Sakkara](https://github.com/atantawi/scheduler-plugins/tree/sakkara) is an experimental
@@ -58,7 +58,7 @@ helm install sakkara-scheduler --namespace sakkara-scheduler --create-namespace
 Optionally, create a config map capturing your cluster's topology as described in the [Sakkara documentation](https://github.com/atantawi/sakkara-deploy/tree/main?tab=readme-ov-file#cluster-topology). This step is optional but recommended for production clusters. If the config map is not present Sakkara will default to a single-level hierarchy containing the Nodes of the cluster.
 {{- end }}
 
-{{ if .OPENSHIFT -}}
+{{ if .RHOAI -}}
 ## Red Hat OpenShift AI
 
 Create the Red Hat OpenShift AI subscription:
@@ -207,7 +207,7 @@ helm upgrade autopilot autopilot/autopilot --install --namespace=autopilot --cre
 
 ### Enabling Prometheus metrics
 
-{{ if .OPENSHIFT -}}
+{{ if .RHOAI -}}
 After completing the installation, manually label the namespace to enable metrics to be scraped by Prometheus with the following command:
 
 ```bash

setup.tmpl/Kubernetes.yaml

@@ -1,6 +1,6 @@
 # Values for Kubernetes v1.29+
 
-OPENSHIFT: false
+RHOAI: false
 VERSION: k8s
 KUBECTL: kubectl
 FAIRSHARE: true

setup.tmpl/RHOAI-v2.13.yaml

@@ -1,6 +1,6 @@
 # Values for RHOAI 2.13
 
-OPENSHIFT: true
+RHOAI: true
 VERSION: RHOAI-v2.13
 KUBECTL: oc
 FAIRSHARE: false

setup.tmpl/RHOAI-v2.16.yaml

@@ -1,6 +1,6 @@
 # Values for RHOAI 2.16
 
-OPENSHIFT: true
+RHOAI: true
 VERSION: RHOAI-v2.16
 KUBECTL: oc
 FAIRSHARE: true

setup.tmpl/RHOAI-v2.17.yaml

@@ -1,6 +1,6 @@
 # Values for RHOAI 2.17
 
-OPENSHIFT: true
+RHOAI: true
 VERSION: RHOAI-v2.17
 KUBECTL: oc
 FAIRSHARE: true

setup.tmpl/TEAM-SETUP.md.tmpl

@@ -5,7 +5,7 @@ A *team* in MLBatch is a group of users that share a resource quota.
 Before setting up your teams and quotas, please read [QUOTA_MAINTENANCE.md](../QUOTA_MAINTENANCE.md)
 for a discussion of our recommended best practices.
 
-{{ if .OPENSHIFT }}
+{{ if .RHOAI }}
 Setting up a new team requires the cluster admin to create a project,
 a user group, a quota, a queue, and the required role bindings as described below.
 
@@ -29,7 +29,7 @@ Bind cluster role to group in namespace:
 Setting up a new team requires the cluster admin to create a namespace,
 a quota, a queue, and the required role bindings as described below.
 
-{{ if .OPENSHIFT }}
+{{ if .RHOAI }}
 Create the namespace:
 ```sh
 {{ .KUBECTL }} create namespace team1