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
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 output Complete at that tier, but later would only output Complete at the .status.conditions[1].type tier after the upgrade.
The text was updated successfully, but these errors were encountered:
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 output
Complete
at that tier, but later would only outputComplete
at the.status.conditions[1].type
tier after the upgrade.The text was updated successfully, but these errors were encountered: