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
I trigger the cronjob by manually via kubernetes dashboard and this jobs ends successfully. However status.lastSuccessfulTime is not updated, thus making it difficult to monitor failed cronjobs.
What happened?
I trigger the cronjob by manually via kubernetes dashboard and this jobs ends successfully. However status.lastSuccessfulTime is not updated, thus making it difficult to monitor failed cronjobs.
Same issue was fixed for kubectl command via kubernetes/kubernetes#118276 but it's still open for dashboards
What did you expect to happen?
status.lastSuccessfulTime should be updated with a timestamp of the succeeded job endTime
How can we reproduce it (as minimally and precisely as possible)?
Install the attached files:
Wait until cronjob has actually trigged, test with
kubectl get cronjob -o jsonpath='{.items[*].status}' | jq
to see that lastScheduleTime and lastSuccessfulTime are populated ok (as expected).
Then apply the fail config-map, now the job will not complete OK:
kubectl apply -f configmap-fail.yaml
Again wait until cronjob has trigged automatically, observe
kubectl get cronjob -o jsonpath='{.items[*].status}' | jq
to see that lastScheduleTime is updated but lastSuccessfulTime is not.
Then apply the "OK" configmap and then create the job manulay via k8s dashboard
when the job has finished and completed ok, observe that lastSuccessfulTime is still not updated.
kubectl get cronjob -o jsonpath='{.items[*].status}'
Wait until next schedule and observe that the field is now updated.
cronjob_test.txt
configmap-fail.txt
configmap-ok.txt
Anything else we need to know?
No response
What browsers are you seeing the problem on?
Chrome
Kubernetes Dashboard version
7.5.0
Kubernetes version
Client Version: v1.30.5 Kustomize Version: v5.0.4-0.20230601165947-6ce0bf390ce3 Server Version: v1.29.11
Dev environment
No response
The text was updated successfully, but these errors were encountered: