Hints: oomkilled

Hint 1

The pod is being killed by the OOM killer. Check pod description: - kubectl describe pod -n grokdevops <pod> | grep -A5 "Last State"

Hint 2

Compare memory usage with limits: - kubectl top pods -n grokdevops - kubectl describe pod -n grokdevops <pod> | grep -A3 Limits - Is the memory limit too low for the workload?

Hint 3

Check the resource limits in the deployment or Helm values: - kubectl get deployment grokdevops -n grokdevops -o jsonpath='{.spec.template.spec.containers[0].resources}' | python3 -m json.tool - The memory limit is likely set too low (e.g., 64Mi for a Python app)

Hint 4

Fix: increase the memory limit in values.yaml (e.g., from 64Mi to 256Mi) and re-deploy, or check for a memory leak in the application.