movilba
MOVILBA-433
· child of MOVILBA-426 Modernize API structure and workflow with ASI health probes Done
Wire ASI health probes into the MovilBA OpenShift Deployment
Done normal
nlnw-lezama-cc
Wire the deployed MovilBA ASI probes into the application Deployment in the GCABA manifests repository. Configure HTTP GET /health/liveness and /health/readiness on port 8080 with the documented reference thresholds: initialDelaySeconds 10, periodSeconds 10, timeoutSeconds 3, failureThreshold 3, successThreshold 1. Acceptance: rendered/applied manifest uses the exact paths, rollout is Ready, liveness returns 200, readiness returns 200 when PostgreSQL is available, and the deployment stops routing traffic on readiness failure.
Activity
-
parent=#3613
-
Assigned network lane is locating the OpenShift Deployment manifest and wiring the already-live health endpoints.
-
Live Deployment inspection: readiness currently GET / on port 8080 (initialDelay 15s, period 10s, timeout 3s); liveness currently GET / on port 8080 (initialDelay 60s, period 20s, timeout 3s). Required /health/readiness and /health/liveness paths are therefore not yet wired. Live app endpoints already return 200; manifest correction remains.
-
Applied to deployment/movilba in movil-ba-dev. Rollout generation 395 observed 395, ready/updated/available=1. Readback confirms readiness=/health/readiness:8080 and liveness=/health/liveness:8080 with initialDelay=10, period=10, timeout=3, failureThreshold=3, successThreshold=1. Both public endpoints returned HTTP 200. Durable evidence: /data-lezama/movilba/evidencia/MOVILBA-433/2026-09-10-probes-apply-readback.md
-
Applied and verified in DEV OpenShift: exact ASI probe paths and thresholds are active; rollout healthy and both endpoints return HTTP 200.
task
5w ago by wi-cli-venus
5w ago
2026-09-10 19:04