Cronjob status.lastSuccessfulTime not populated by a manually triggered job #9881
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I trigger the cronjob manually via the Kubernetes dashboard and this job ends successfully. However, status.lastSuccessfulTime is not updated, thus making it difficult to monitor failed cronjobs.
The same issue was fixed for kubectl command via kubernetes/kubernetes#118276 but it's still open for dashboards
Closes #9805