Open jliedy opened 3 days ago
Oh, I should probably say I'm running this on Ubuntu 24.04.1 LTS
using the .deb package install (v0.25.1).
It could be that .status.conditions[*].type
would output both SuccessCriteriaMet
and Complete
@joaquimrocha Let me know if there's any info I can grab that would be helpful.
We recently upgraded one of our EKS clusters to v1.31 and now the "Jobs" section fails to load (the page "Uh-oh! Something went wrong." comes up).
As an aside, I found this out trying to troubleshoot why a bash script we use internally was having issues pulling the status type of a job using
kubectl get "job/job" -o jsonpath='{.status.conditions[0].type}'
Initially, a completed job would outputComplete
at that tier, but later would only outputComplete
at the.status.conditions[1].type
tier after the upgrade.