Be able to generate MLOps bundle

[kimwnasptd]

Why it needs to get done

We need to be able to have a way to define a "full mlops" bundle, which we could use at least for testing.

We have seen the need for this at least in two places:

• Running all of our UATs, which also need MLFlow
• Running airgapped tests, than also need MLFlow and resource dispatcher
• In the future when we'd like to verify COS integration

we'll need to have a way to use (either a script to produce it, or have it committed) a bundle that includes all charms and their relations, and not just Charmed Kubeflow.

What needs to get done

Not fully sure about which approach to take yet, and open to discussion.

Initially I had in mind of having a bundle committed, but I think this will create a more maintenance burden. So the second approach I had in mind was to have a script that takes as inputs:

1. An initial CKF bundle
2. The risk (or could potentially deduce from bundle)

and the script would then generate the full bundle

When is the task considered done

When we have a way to have a full mlops bundle that we will be able to use at least to run tests for

• UATs
• Airgapped tests

[syncronize-issues-to-jira[bot]]

Thank you for reporting us your feedback!

The internal ticket has been created: https://warthogs.atlassian.net/browse/KF-5133.

This message was autogenerated

[ca-scribner]

Charmed Kubernetes treat their bundles as artifacts, not inputs. They have scripts that assemble their bundle from templates. So you might have something like:

• kubeflow.j2
• mlflow.j2
• ...

or maybe lower level might be more helpful

• kubeflow-profiles.j2
• kubeflow-pipelines.j2
• ...

Then we execute kubeflow-bundle-generator --template kubeflow.j2 --template mlflow.j2 --channel 1.2.3/stable

(although in this simple example, I'm ignoring how the different templates need different channels... something to figure out later :D )