fix: self-healing patch for PodCrash in crash-test-55b8b665f4-hjqjs

[aftabkh4n]

Self-Healing Patch

This PR was opened automatically by the self-healing-k8s system.

Failure detected

• Pod: crash-test-55b8b665f4-hjqjs
• Namespace: default
• Type: PodCrash
• Detected at: 2026-04-20 06:20:38 UTC

Root cause

The application is unable to establish a connection to the PostgreSQL database at postgres://db:5432. The pod crashes immediately after startup with exit code 1 when the database connection attempt fails. This indicates either the database service is unreachable, the hostname 'db' cannot be resolved, the database is not running, or network connectivity between the pod and database is broken.

Severity

Critical

Suggested fix

1. Verify the PostgreSQL service named 'db' exists and is running in the cluster using 'kubectl get svc db'. 2) Check if the database pod is ready using 'kubectl get pods -l app=postgres'. 3) Confirm network connectivity from the crash-test pod to the database pod using 'kubectl exec crash-test-55b8b665f4-hjqjs -- nc -zv db 5432'. 4) Verify the database credentials and connection string are correct in the application configuration. 5) Check database logs for connection errors. 6) Ensure the database is fully initialized and accepting connections. 7) Add startup probes or init containers to delay pod startup until the database is ready.

Proposed code change

Add an initContainer to the deployment to wait for database readiness:
apiVersion: apps/v1
kind: Deployment
metadata:
name: crash-test
spec:
template:
spec:
initContainers:
- name: wait-for-db
image: busybox:1.28
command: ['sh', '-c', 'until nc -z db 5432; do echo waiting for db; sleep 2; done']
containers:
- name: app
image: your-app:latest

---

Generated by self-healing-k8s