Configure a Custom Bucket for Pipelines

This guide describes how to update the object storage bucket employed by Pipelines.

Requirements

  • A CKF deployment. See Get started for more details.

  • Juju version >= 3.4.

  • Juju admin access to the kubeflow model.

  • An object storage bucket, for Pipelines to store its artifacts, to replace the default/current bucket with.

Configure Pipelines’ Charms with a Custom Bucket

After defining an environment variable for your bucket name, for your convenience:

BUCKET_NAME="your-bucket-name"

The following charms need to have their respective bucket configurations updated:

Argo Controller

Update the name of the bucket via its bucket configuration option, e.g.:

juju config argo-controller bucket=${BUCKET_NAME}

KFP API

Update the name of the bucket via its object-store-bucket-name configuration option, e.g.:

juju config kfp-api object-store-bucket-name=${BUCKET_NAME}

KFP Profile Controller

Update the default pipeline root for pipeline Runs across all Profiles, which includes the schema for, the name of and the path to the bucket, via its default_pipeline_root configuration option, e.g.:

juju config kfp-profile-controller default_pipeline_root=minio://${BUCKET_NAME}/v2/artifacts

Note

In Charmed Kubeflow, Pipelines can only be configured with the MinIO schema.

This automatically creates a ConfigMap named kfp-launcher in each Profile

Note

For this configuration change to take effect, existing ConfigMaps — if any — named kfp-launcher in the namespace of each Profile of interest have to be manually deleted after the configuration change is applied, so that they are automatically recreated with the updated default pipeline root. Refer to this issue for details.