Skip to content

4. Using Operator in Dev Mode

Vaishnavi Hire edited this page Mar 25, 2024 · 1 revision

Operator API exposes fields under devFlags that can be used to deploy custom manifests. This configuration overrides the local manifests pulled using script.

API Spec for devFlags


 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
   

DevFlags Example

Deploy Manifests with a manifests tag/branch

spec:
 components:
   dashboard:
     devFlags:
       manifests:
        - contextDir: manifests
          uri: https://github.com/opendatahub-io/odh-dashboard/tarball/v2.15.0-incubation

Deploy Manifests with custom source path

spec:
 components:
   dashboard:
     devFlags:
       manifests:
        - contextDir: manifests
          sourcePath: overlays/incubation
          uri: https://github.com/opendatahub-io/odh-dashboard/tarball/v2.15.0-incubation

Deploy custom manifests for component with reference to multiple repos

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'