Upgrade Notes

Notices and breaking changes when you upgrade Kubeflow Pipelines Backend

This page introduces notices and breaking changes you need to know when upgrading Kubeflow Pipelines Backend.

For upgrade instructions, refer to distribution specific documentations:

Upgrading to v2.0

  • Notice: In v2.0 frontend, run metrics columns are deprecated in the run list page, but users can still get the same information by using KFPv2 Scalar metrics

Upgrading to v1.7

  • Breaking Change: Metadata UI and visualizations are not compatible with TensorFlow Extended (TFX) <= v1.0.0. Upgrade to v1.2.0 or above, refer to Kubeflow Pipelines Backend and TensorFlow Extended (TFX) compatibility matrix.

  • Notice: Emissary executor (Alpha), a new argo workflow executor is available as an option. Due to Kubernetes deprecating Docker as a container runtime after v1.20, emissary may become the default workflow executor for Kubeflow Pipelines in the near future.

    For example, the current default docker executor does not work on Google Kubernetes Engine (GKE) 1.19+ out of the box. To use docker executor, your cluster node image must be configured to use docker (deprecated) as container runtime.

    Alternatively, using emissary executor (Alpha) removes the restriction on container runtime, but note some of your pipelines may require manual migrations. The Kubeflow Pipelines team welcomes your feedback in the Emissary Executor feedback github issue.

    For detailed configuration and migration instructions for both options, refer to Argo Workflow Executors.

  • Notice: Kubeflow Pipelines SDK v2 compatibility mode (Beta) was recently released. The new mode adds support for tracking pipeline runs and artifacts using ML Metadata. In v1.7 backend, complete UI support and caching capabilities for v2 compatibility mode are newly added. We welcome any feedback on positive experiences or issues you encounter.


Was this page helpful?