When using the Kubeflow Pipelines (KFP) UI to search for a pipeline version during run creation, the request fails with an error if the backend is KFP v1.

Error retrieving resources
Invalid input error: failed to parse valid filter … unknown field "operation" in api.Predicate

Environment

• How did you deploy Kubeflow Pipelines (KFP)?
  Kubeflow manifest 1.9.1 (multi-user)
  k8s version: 1.29 (AWS EKS)

KFP version:

• kubeflow pipeline 2.3.0
• Argo-workflow: v3.4.17
• KFP Python SDK: 1.8.2

Root Cause

• The KFP UI always sends the filter parameter using the field operation.

-This field is supported in KFP v2, but not in KFP v1.

• In KFP v1, the correct field is op.

• The UI does not currently detect whether it’s connected to a v1 or v2 backend, and therefore sends an incompatible filter in v1 environments.

Steps to reproduce

• Open the Kubeflow Pipelines UI connected to a KFP v1 backend.

• Create or edit a run.

• In the Choose a pipeline version dialog, try to search for a version by name using the search bar.

• Observe the error.

Expected result

The UI should either:

• Detect the backend version (v1 vs v2) and use the appropriate filter field (op for v1, operation for v2), or

• Fallback gracefully without error.

Impacted by this bug? Give it a 👍.