Pipeline runs do not appear in dashboard

[Rui Vasconcelos]

Running Kubeflow on Microk8s v1.20.7, the example pipeline from the dashboard "[Tutorial] Data passing in python components".

The pods are spun up:
kubeflow file-passing-pipelines-dxr5d-211174895 0/2 Completed 0 13m
kubeflow file-passing-pipelines-dxr5d-1572945527 0/2 Completed 0 13m
kubeflow file-passing-pipelines-dxr5d-2742909771 0/2 Completed 0 13m
kubeflow file-passing-pipelines-dxr5d-3773469760 0/2 Completed 0 12m
kubeflow file-passing-pipelines-dxr5d-1858922284 0/2 Completed 0 12m
kubeflow file-passing-pipelines-dxr5d-1875699903 0/2 Completed 0 12m

However, in the Kubeflow dashboard, the "Runs" tab has zero runs - "No available runs found in this namespace".

The "Experiments(KFP)" tab has "Error: failed to retrieve list of experiments. click Details for more information.".

Details:
====
An error occurred

{"error":"Invalid input error: In single-user mode, ListExperiment cannot filter by namespace.","code":3,"message":"Invalid input error: In single-user mode, ListExperiment cannot filter by namespace.","details":[{"@type":"type.googleapis.com/api.Error","error_message":"In single-user mode, ListExperiment cannot filter by namespace.","error_details":"Invalid input error: In single-user mode, ListExperiment cannot filter by namespace."}]}
======

[Dominik Fleischmann (dominik.f)]

This looks like a duplicate to this bug: https://bugs.launchpad.net/kubeflow-bundle/+bug/1929248

This should be fixed in the latest bundle which you can install on microk8s the following way:

microk8s enable kubeflow --bundle=cs:kubeflow

[Rui Vasconcelos (ruivasconcelos)]

Thank you for the clarification, Dominik! I was not 100% sure it was the same bug, so I thought I might report it :)

For future reference, this has been moved to Fix Released, nevertheless, no user is able to find the patch as there is no documentation that guides him to try:

microk8s enable kubeflow --bundle=cs:kubeflow

I would like us to get into the habit of solving for the user. If he can't find the fix, to him it is not fixed.

[Dominik Fleischmann (dominik.f)]

The fix is released to the stable channel for the kubeflow bundles, as we have talked before, for releasing on microk8s we currently rely on the microk8s release process.There are current discussions of pointing directly to the latest stable bundle in the microk8s addon to avoid this process.

With this bug tracker being focused on the kubeflow bundle itself and not the microk8s addon, the fix can be officially considered released.

[Rui Vasconcelos (ruivasconcelos)]

I understand. Let's figure out the best way to make it a good experience. :)