You have never seen wastes-1gbotgo before. Someone wants a status report in ten minutes. Start wide, then narrow:

kubectl get deploy,pods -n wastes-1gbotgo
kubectl events -n wastes-1gbotgo --types=Warning
kubectl top pods -n wastes-1gbotgo --sort-by=memory

Answer five questions:

1. Which Deployment's Pod keeps restarting? The Warning events name it.
2. Which resource does the scheduler say the Pending Pod lacks? Its PodScheduled condition carries the message.
3. Besides the restarter, which Deployment reports Available=False? A custom column over .status.conditions shows every Deployment at once.
4. Which Pod uses the most memory?
5. How many Pods are not in the Running phase? A field selector counts them.

Then clean up: delete the Pod that already finished, and give the restarter the variable its logs ask for so it comes up Ready.

kubectl get pods -n wastes-1gbotgo --field-selector status.phase=Succeeded -o name | xargs kubectl delete -n wastes-1gbotgo
kubectl logs deploy/market-api -n wastes-1gbotgo --previous --tail=3