-
Notifications
You must be signed in to change notification settings - Fork 210
4. Using Operator in Dev Mode
Gerard Ryan edited this page Sep 18, 2025
·
4 revisions
In ODH 3, the Dev Flags approach used in ODH 2 is removed, and the new approach is documented in the README.md under hack/component-dev/ in the repository.
Operator API exposes fields under devFlags that can be used to deploy custom manifests. This configuration overrides the local manifests pulled using script.
devFlag is an internal tool which mainly helps developers integrate their code. It is not a supported feature in downstream RHOAI. It might get deprecated in future release.
devFlags:
manifests:
- uri: <github.repo>/tarball/<branch/tag>
contextDir: <path to manifest folder>
sourcePath: <path to start kustomize build> -----------------> This can be `base`, `overlays/x`, `default`, `custom` etc
spec:
components:
dashboard:
devFlags:
manifests:
- contextDir: manifests
uri: https://github.com/opendatahub-io/odh-dashboard/tarball/v2.15.0-incubation
spec:
components:
dashboard:
devFlags:
manifests:
- contextDir: manifests
sourcePath: overlays/incubation
uri: https://github.com/opendatahub-io/odh-dashboard/tarball/v2.15.0-incubation
spec:
components:
workbenches:
devFlags:
manifests:
- contextDir: components/odh-notebook-controller/config
uri: 'https://github.com/opendatahub-io/kubeflow/tarball/v1.7.0-3'
- contextDir: components/notebook-controller/config
uri: 'https://github.com/opendatahub-io/kubeflow/tarball/v1.7.0-3'
- contextDir: manifests
uri: 'https://github.com/opendatahub-io/notebooks/tarball/v1.10.0'
kserve:
devFlags:
manifests:
- contextDir: config
sourcePath: overlays/odh
uri: 'https://github.com/opendatahub-io/kserve/tarball/mybranch1'
- contextDir: config
sourcePath: ''
uri: 'https://github.com/opendatahub-io/odh-model-controller/tarball/mybranch2'