Kubernetes deployment health from outside the cluster
Readiness probes pass inside the pod, but no one sees that the LB refused to route traffic to the new deploy.
Recipe
yaml
# Экспонируйте health endpoint через Ingress, а не только ClusterIP
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
name: app-healthz
spec:
rules:
- host: app.example.com
http:
paths:
- path: /readyz
pathType: Exact
backend: { service: { name: app, port: { number: 80 } } }Same thing in Enterno.io
Add an Enterno monitor to https://app.example.com/readyz. If cluster DNS breaks access to /readyz — you learn about it before users do.