You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Showing pod events in the KFP v2 Web UI like it did in KFP v1.
What is the use case or pain point?
When one creates a component that can never run, e.g. because one made it use a secret that doesn't exist, the web UI shows it in a "running" state forever. The web UI has no way of showing the user what the issue is, even though this information is often available from the pod's events.
Is there a workaround currently?
Look into the events "by hand", e.g. using kubectl, k9s, Lens etc. This is too technical for some users.
Feature Area
/area frontend
What feature would you like to see?
Showing pod events in the KFP v2 Web UI like it did in KFP v1.
What is the use case or pain point?
When one creates a component that can never run, e.g. because one made it use a secret that doesn't exist, the web UI shows it in a "running" state forever. The web UI has no way of showing the user what the issue is, even though this information is often available from the pod's events.
Is there a workaround currently?
Look into the events "by hand", e.g. using kubectl, k9s, Lens etc. This is too technical for some users.
Example
Pipeline
needs kfp-kubernetes installed
Frontend
Frontend look like it's running, but logs are not available
Events
Events show what the actual issue is
Love this idea? Give it a 👍.
The text was updated successfully, but these errors were encountered: