[feature] Support pipeline versions in sample pipelines

[mprahl]

Feature Area

/area backend
/area samples

What feature would you like to see?

Allow sample pipelines to be treated more like default/system pipelines that are provided by the platform administrator. Currently, sample pipelines are only imported once on the first start. It'd be nice if you could upload new pipeline versions of a sample pipeline and have more control over the sample pipeline version names.

Desired outcome:

• Sample pipelines are always uploaded on API server startup. If the sample pipeline version already exists, it is not uploaded again (i.e. no diff checking or updating).
• A version name and version description can be specified on a sample pipeline.
• Sample pipelines can have multiple pipeline versions.

One idea is to change the sample config struct to include these optional new fields that can be set in the sample_config.json file:

type config struct {
	Name        string
	Description string  // <-- only used if this is the first pipeline version
	File        string
	VersionName string // <-- optional new field
	VersionDescription string // <-- optional new field
}

What is the use case or pain point?

A Kubeflow Pipelines distribution can leverage sample pipelines to include system/out of the box pipelines that are updated with new pipeline versions when the Kubeflow Pipelines distribution updates.

Is there a workaround currently?

No specific workaround other than writing a separate utility that performs the upload.

---

Love this idea? Give it a 👍.