Skip to content
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

Open
geier opened this issue Apr 24, 2024 · 5 comments · May be fixed by #11226
Open

[feature] Show Pod Events in KFP v2 UI #10740

geier opened this issue Apr 24, 2024 · 5 comments · May be fixed by #11226

Comments

@geier
Copy link
Contributor

geier commented Apr 24, 2024

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

from kfp import dsl
from kfp.client import Client
from kfp import kubernetes


@dsl.component
def hello():
    print('hello world!')

    
@dsl.pipeline
def example_pipeline():   
    task = hello()
    kubernetes.use_secret_as_env(task, "does-not-exist", {'key': 'value'})


client = Client()
run = client.create_run_from_pipeline_func(example_pipeline)

Frontend

Frontend look like it's running, but logs are not available
image

Events

Events show what the actual issue is

image

Love this idea? Give it a 👍.

Copy link

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 github-actions bot added the lifecycle/stale The issue / pull request is stale, any activities remove this label. label Jun 24, 2024
@geier
Copy link
Contributor Author

geier commented Jun 24, 2024

is there a command to unstale this?

@stale stale bot removed the lifecycle/stale The issue / pull request is stale, any activities remove this label. label Jun 24, 2024
Copy link

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 github-actions bot added the lifecycle/stale The issue / pull request is stale, any activities remove this label. label Aug 24, 2024
@ElayAharoni
Copy link
Contributor

/assign

@stale stale bot removed the lifecycle/stale The issue / pull request is stale, any activities remove this label. label Aug 29, 2024
@ElayAharoni ElayAharoni linked a pull request Sep 19, 2024 that will close this issue
@rimolive
Copy link
Member

rimolive commented Oct 1, 2024

/lifecycle frozen

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants