Enable or Disable Tools¶

Customize which tools are in your deployKF platform.

Overview¶

Every tool which is available in deployKF can be enabled or disabled with its corresponding enabled value. This allows you to build a platform that fits your needs by including only the tools you want to use.

The sample values for each release of deployKF will have all tools enabled, along with on-cluster versions of any external dependencies required by those tools. If you are using the sample values as a base for your own configuration and wish to disable a specific tool, see the following sections for instructions.

Info

After updating your values, remember to sync all applications to apply the changes to your cluster.

Additionally, because deployKF will never delete namespaces (except profile namespaces), you may want to manually clean up those that are no longer needed to avoid the deploykf-app-of-apps always being out-of-sync.

Kubeflow Tools¶

deployKF includes a number of tools from the Kubeflow ecosystem, which can be enabled or disabled individually.

Kubeflow Pipelines¶

Disable Kubeflow Pipelines

The following values will disable Kubeflow Pipelines and its dependencies Argo Workflows, MinIO, and MySQL:

deploykf_opt:
  deploykf_minio:
    ## NOTE: other tools may still require MinIO to be enabled, unless they
    ##       are also disabled or connected to an external object store
    enabled: false

  deploykf_mysql:
    ## NOTE: other tools may still require MySQL to be enabled, unless they
    ##       are also disabled or connected to an external database
    enabled: false

kubeflow_dependencies:
  kubeflow_argo_workflows:
    enabled: false

kubeflow_tools:
  pipelines:
    enabled: false

Kubeflow Notebooks¶

Disable Kubeflow Notebooks

The following values will disable Kubeflow Notebooks:

kubeflow_tools:
  notebooks:
    enabled: false

Kubeflow Katib¶

Disable Kubeflow Katib

The following values will disable Kubeflow Katib and its dependency MySQL:

deploykf_opt: 
  deploykf_mysql:
    ## NOTE: other tools may still require MySQL to be enabled, unless they
    ##       are also disabled or connected to an external database
    enabled: false

kubeflow_tools:
  katib:
    enabled: false

Kubeflow Training Operator¶

Disable Kubeflow Training Operator

The following values will disable the Kubeflow Training Operator:

kubeflow_tools:
  training_operator:
    enabled: false

Kubeflow Volumes¶

Disable Kubeflow Volumes

The following values will disable Kubeflow Volumes:

kubeflow_tools:
  volumes:
    enabled: false

Kubeflow TensorBoards¶

Disable Kubeflow TensorBoards

The following values will disable Kubeflow TensorBoards:

kubeflow_tools:
  tensorboards:
    enabled: false

Kubeflow PodDefaults Webhook¶

Disable Kubeflow PodDefaults Webhook

The following values will disable the Kubeflow PodDefaults Webhook:

kubeflow_tools:
  poddefaults_webhook:
    enabled: false

Last update: 2024-08-30
Created: 2024-08-30