Three objects in plains-jfo44s. Read before you act.

kubectl get deploy,cronjobs -n plains-jfo44s

market-web: a rollout that does not move

kubectl rollout status deploy/market-web -n plains-jfo44s
kubectl get deploy market-web -n plains-jfo44s -o jsonpath='{.spec.paused}'

rollout status waits on 0 out of 3 new replicas and gives up. The template says nginx:1.26; every Pod still runs nginx:1.27. The Deployment is paused. Resume it and the rollout completes on its own.

market-worker: READY 0/0

kubectl get deploy market-worker -n plains-jfo44s

A Deployment with replicas: 0 is healthy and useless. The worker needs at least 2.

report: SUSPEND True

kubectl get cronjobs -n plains-jfo44s

The report CronJob is suspended. Un-suspend it, and while you are in the spec, set concurrencyPolicy: Forbid so two reports never run at once:

kubectl patch cronjob report -n plains-jfo44s -p '{"spec":{"suspend":false,"concurrencyPolicy":"Forbid"}}'

kubectl apply of a corrected manifest works too.