Return Kubernetes Events for a certain task #5089
Replies: 2 comments 1 reply
-
|
I think the reason why the event is often outdated for several plugins is that the phase version is only increased consistently in the pod plugin (see here). If you don't increase the version when the "reason changes", no new event is sent to propeller. |
Beta Was this translation helpful? Give feedback.
-
|
Yes lets update the phasing system. Sending k8s events back is dangerous. This can be a lot of data and is not optimal. Most users will not have a very complicated setup and to serve most users, we need to keep it simple, scalable and easy |
Beta Was this translation helpful? Give feedback.
-
|
2024-04-25 Contributors meetup notes: do not proceed to RFC or implementation as there are UX concerns. |
Beta Was this translation helpful? Give feedback.
-
Motivation
Often tasks are displayed as running, like in the screenshot shown below:
In reality the pod cannot be started, because the image is invalid and cannot be pulled. The user should get some feedback in the field that is highlighted. It looks like it is coming from task executions API endpoint. The data seems to be coming from a database table and is outdated.
Users are therefore often confused, why their workloads do not complete despite being shown running for a long time.
Functionality
The field providing feedback about the status of the task should also contain relevant Kubernetes Events that are kept up to date to provide meaningful feedback.
Beta Was this translation helpful? Give feedback.
All reactions