-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[feature] Show Pod Events in KFP v2 UI #10740
Comments
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
github-actions
bot
added
the
lifecycle/stale
The issue / pull request is stale, any activities remove this label.
label
Jun 24, 2024
is there a command to unstale this? |
stale
bot
removed
the
lifecycle/stale
The issue / pull request is stale, any activities remove this label.
label
Jun 24, 2024
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
github-actions
bot
added
the
lifecycle/stale
The issue / pull request is stale, any activities remove this label.
label
Aug 24, 2024
/assign |
stale
bot
removed
the
lifecycle/stale
The issue / pull request is stale, any activities remove this label.
label
Aug 29, 2024
/lifecycle frozen |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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: