Dead jobs don't leave the interface #6976
Replies: 3 comments 3 replies
-
|
This could be a stale cache problem. Is this resolved by visiting the cluster page and clicking the "Invalidate cache" button?
|
Beta Was this translation helpful? Give feedback.
-
|
I ran the cache invalidation process, but the jobs are still continuing on the interface. |
Beta Was this translation helpful? Give feedback.
-
|
Are you able to click on an individual job and show the live object YAML? This should fail if the object doesn't truly exist because we query this from K8s API server upon the panel load. |
Beta Was this translation helpful? Give feedback.
-
|
I don't see anything on the live manifests |
Beta Was this translation helpful? Give feedback.
-
|
These look like older completed CronJob jobs. I think you may have the misunderstanding that that these Job are supposed to disappear. CronJobs keep 3 successful and 1 failed by default. See: |
Beta Was this translation helpful? Give feedback.
-
|
@jessesuen, I already have it configured in cronjobs, the job is deleted in kubernetes by this function, it only continues in the argo interface.
|
Beta Was this translation helpful? Give feedback.
-
Hello, I have a problem with jobs in the argocd interface, I have jobs that have already been removed from kubernetes after a successful run for more than 15 days, only jobs remain in the interface even after being removed from k8s.
Beta Was this translation helpful? Give feedback.
All reactions