Skip to content

Kubeflow Pipelines (Kubernetes API mode) error: Failed to get a pipeline (v1beta1) due to error fetching the latest pipeline version. #13216

@rckr2710

Description

@rckr2710

I am encountering an issue while using Kubeflow Pipelines in Kubernetes API mode, likely related to a CRD version mismatch.

After generating the pipeline manifest and applying it using:

kubectl apply -f .yaml

the pipeline resource is successfully created and visible in the Kubeflow UI. However, when attempting to open or interact with the pipeline, the following error occurs:

Failed to get a pipeline (v1beta1) due to error fetching the latest pipeline version.
ResourceNotFoundError: PipelineVersion latest not found

Additional Observation:

The installed CRDs in the cluster are using v2beta1
Kubeflow Pipelines appears to be expecting or operating with v1beta1 CRDs

This suggests there may be a version incompatibility between the installed CRDs and the Kubeflow Pipelines backend/UI components.

Steps to Reproduce:

Generate pipeline manifest (compiled pipeline YAML).

Apply the manifest:

kubectl apply -f .yaml
Open Kubeflow Pipelines UI.
Navigate to the created pipeline.

Expected Behavior:

The pipeline should load correctly in the UI.
The latest pipeline version should be available and accessible.

Actual Behavior:

The pipeline is visible in the UI.

Accessing it results in:

ResourceNotFoundError: PipelineVersion latest not found

Error Image:

Image

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions