Operator/rhoai #97

hultzj · 2026-01-14T03:41:10Z

No description provided.

- Added "Quick Start from Source" and updated "Quick Start (OCI)" for clarity. - Included a new section for "Adding New Operators" to guide contributions. - Revised development workflow steps for better clarity and organization.

…atching

rhoai branch

Refactor RHOAI policy documentation and values.yaml.

…uired operators for RHOAI 3.0, including GitOps, ACM, Serverless, Service Mesh, Pipelines, Node Feature Discovery, and NVIDIA GPU Operator.

GPU operator

…rator policy to enforce OwnNamespace install mode, while cleaning up RHOAI policy configuration by removing unnecessary fields.

Update .gitignore to exclude my-values.yaml and modify NVIDIA GPU ope…

- Introduced new dashboard configuration options in values.yaml for tracking, model features, GenAI features, and notebook controller settings. - Updated policy-rhoai-config.yaml to enforce the new dashboard settings through a ConfigurationPolicy for OdhDashboardConfig.

Add OdhDashboardConfig settings to RHOAI policy

- Added detailed steps for installing OpenShift GitOps and Red Hat ACM operators as prerequisites for deploying AutoShift. - Updated deployment steps to include configuring OCI registry credentials, applying cluster labels, and verifying deployment. - Introduced new ConfigurationPolicies for KnativeServing and RHOAI dashboard route in policy-rhoai-config.yaml. - Updated values.yaml for serverless and servicemesh3 policies to include configurations for KnativeServing and Istio.

RHOAI policies

…ft and NVIDIA GPU operator - Corrected the OCI registry path for AutoShift installation and updated the values file reference. - Clarified steps for moving clusters to the 'hub' ClusterSet and applying AutoShift labels for operator installation. - Enhanced NVIDIA GPU operator policy documentation to emphasize the requirement of Node Feature Discovery (NFD) for GPU detection. - Updated values.yaml and policy templates to reflect changes in GPU operator configurations and dependencies.

Update deployment documentation and policy configurations for AutoShi…

- Added new ConfigurationPolicies for DataScienceCluster initialization and management, including `rhoai-dsc-bootstrap` and `rhoai-dsc`. - Updated README.md to include detailed descriptions of new ConfigurationPolicies and their roles in RHOAI 3.0. - Included troubleshooting steps for components stuck in "Removed" state and clarified management state handling for DataScienceCluster. - Expanded values.yaml to incorporate new dashboard configuration options and model registry settings.

Enhance RHOAI policy documentation and configuration

andymiller96

Rough first pass at PR review

andymiller96 · 2026-01-16T15:16:48Z

Untitled

Probably shouldn't commit a file named "Untitled" in the base directory. Or anywhere for that matter.

Removed I missed that :(

andymiller96 · 2026-01-16T15:27:58Z

policies/servicemesh3/values.yaml

+  istio:
+    name: default
+    namespace: istio-system
+    version: "v1.26.2"  # Must match servicemesh3 operator version


Why are we hard-coding a version? Same for line 29.

andymiller96 · 2026-01-16T15:31:36Z

policies/servicemesh3/values.yaml

  name: servicemeshoperator3
  namespace: openshift-operators
-  channel: stable
+  channel: stable-3.2


Don't need to default to 3.2 when it's overridden by the template
example here:

autoshiftv2/autoshift/values.hub.yaml

Line 43 in 605402c

servicemesh3-channel: stable-3.2

Should we just leave it blank/comment it out or does it affect the install if the hub.yaml value over rides the values.yaml.

…d file and update values.hub.yaml to include commented-out sections for Istio and GPU operator settings.

andymiller96 · 2026-01-21T15:36:34Z

Let's kill the helm charts if there's an equivalent OperatorPolicy for those operators. @hultzj

andymiller96

Remove unnecessary helm charts
Move quickstart to its own .md
Update CNI namespace
Address other random comments (versions, etc.)
Have Ben review the stuff he's tagged in

andymiller96 · 2026-01-21T15:24:35Z

policies/servicemesh3/templates/policy-servicemesh3-config.yaml

+                  name: {{ .Values.servicemesh3.istioCni.name | default "default" }}
+                spec:
+                  version: {{ .Values.servicemesh3.istioCni.version | default "v1.24.3" | quote }}
+                  namespace: {{ .Values.servicemesh3.istio.namespace | default "istio-system" }}


istio-cni should be in its own namespace, typically "istio-cni"

andymiller96 · 2026-01-21T15:33:17Z

docs/quickstart-oci.md

move from quickstart-oci to something like quickstart-rhoai.

platform version update from 4.18 to 4.20 probably needs to happen all across the codebase as its own PR @bcarr-rh

Yep that is on my todo list

andymiller96 · 2026-01-21T15:33:42Z

policies/node-feature-discovery/templates/policy-node-feature-discovery-instance.yaml

@bcarr-redhat

I feel like this breaks the nodeFeatureDiscovery. I think if you dont use it you can just disable it in a rhoai values file

bcarr-rh · 2026-01-21T17:25:40Z

docs/README.md


 ### Development
 - **[Developer Guide](developer-guide.md)** - Contributing to AutoShift and advanced configuration
+- **[Adding New Operators](adding-new-operators.md)** - Step-by-step guide to add operators and contribute upstream


I think this and the Developer Guide are meant to be the same thing

bcarr-rh · 2026-01-21T17:26:33Z

docs/deploy-oci.md


 ## Deployment Steps

-### Step 1: Configure OCI Registry Credentials


The oci deployment should all be using oci not the local helm at all. The bootstraps are in oci as well and there should be scripts to deploy bootstrap with oci

bcarr-rh · 2026-01-21T17:27:32Z

docs/deploy-oci.md

 ```

-### Step 3: Verify Deployment
+### Step 5: Move Cluster to Hub ClusterSet (Required)


The labels are actually applied to the cluster through a labels policy and shouldnt be applied manually

bcarr-rh · 2026-01-21T17:28:09Z

docs/quickstart-oci.md

Yep that is on my todo list

bcarr-rh · 2026-01-21T17:29:36Z

policies/node-feature-discovery/templates/policy-node-feature-discovery-instance.yaml

I feel like this breaks the nodeFeatureDiscovery. I think if you dont use it you can just disable it in a rhoai values file

bcarr-rh · 2026-01-21T17:29:54Z

policies/node-feature-discovery/values.yaml

  operatorGroupName: openshift-nfd-operator
  targetNamespaces: # Target namespaces for namespace-scoped operators
    - openshift-nfd
-  operandImage: 'registry.redhat.io/openshift4/ose-node-feature-discovery-rhel9:v4.18'


Is this needed?

bcarr-rh · 2026-01-21T17:31:00Z

policies/nvidia-gpu/values.yaml

@@ -0,0 +1,100 @@
+# Default values for nvidia-gpu


Should any of these new values be configurable per cluster? If so you may want to have these as defaults and add new labels

hultzj and others added 30 commits January 2, 2026 11:38

Fix command for patching AutoShift application in quickstart guide

3d54844

Update quickstart guide to improve clarity on AutoShift application p…

22b979d

…atching

Merge pull request #86 from hultzj/main

b691526

rhoai branch

Refactor RHOAI policy documentation and values.yaml.

16b77cc

Merge pull request #87 from hultzj/main

615b0bb

Refactor RHOAI policy documentation and values.yaml.

Add an operator to install and configure Nvidia gpu opertor

3b2cc6c

Update quickstart-oci.md to reflect new OpenShift version and add req…

30db5fd

…uired operators for RHOAI 3.0, including GitOps, ACM, Serverless, Service Mesh, Pipelines, Node Feature Discovery, and NVIDIA GPU Operator.

Merge pull request #88 from hultzj/main

ecad0b6

GPU operator

Update .gitignore to exclude my-values.yaml and modify NVIDIA GPU ope…

4309ec4

…rator policy to enforce OwnNamespace install mode, while cleaning up RHOAI policy configuration by removing unnecessary fields.

Merge pull request #89 from hultzj/main

07f4edf

Update .gitignore to exclude my-values.yaml and modify NVIDIA GPU ope…

Merge pull request #90 from hultzj/main

697dac2

Add OdhDashboardConfig settings to RHOAI policy

Merge pull request #91 from hultzj/main

658050c

RHOAI policies

Merge pull request #92 from hultzj/main

96ffb1a

Update deployment documentation and policy configurations for AutoShi…

Merge pull request #93 from hultzj/main

cffbbde

Enhance RHOAI policy documentation and configuration

Adjusted policy-rhoai-config.yaml

15b22f2

Update RHOAI policy documentation and configuration for v2 API

9f7945d

Refactor DataScienceCluster configuration in policy-rhoai-config.yaml

9dba9c0

Change api to v2

96e6893

Update policy-rhoai-config.yaml

a5cb224

Update policy-rhoai-config.yaml to use v2 API for DataScienceCluster

e496b24

Fix recreateOption placement

44548fa

Refactor policy-rhoai-config.yaml to align with v2 API

b376c93

Refactor operator installation policies

43b9c78

Update NVIDIA GPU and Node Feature Discovery policies

3f9a63e

Remove operandImage from values.yaml

b887aec

hultzj requested a review from bcarr-rh January 14, 2026 03:41

bcarr-rh requested a review from andymiller96 January 15, 2026 15:39

andymiller96 reviewed Jan 16, 2026

View reviewed changes

Remove deprecated configuration for RHOAI and NVIDIA GPU from Untitle…

f30de92

…d file and update values.hub.yaml to include commented-out sections for Istio and GPU operator settings.

andymiller96 requested changes Jan 21, 2026

View reviewed changes

bcarr-rh reviewed Jan 21, 2026

View reviewed changes


		## Deployment Steps

		### Step 1: Configure OCI Registry Credentials

Operator/rhoai #97

Are you sure you want to change the base?

Operator/rhoai #97

Uh oh!

Conversation

hultzj commented Jan 14, 2026

Uh oh!

andymiller96 left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

andymiller96 commented Jan 21, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

andymiller96 left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

5 participants

andymiller96 commented Jan 21, 2026 •

edited

Loading