Grep upstream timeouts in logs ingress-nginx
Hunt backend timeouts and client-aborted requests; note: 499 means client closed before upstream replied
kubectl logs -n ingress-nginx deploy/ingress-nginx-controller --tail=2000 | grep -iE 'upstream timed out|504|499'
more ingress-nginx
all 7 commands →
Canary traffic split annotation
kubectl annotate ingress <name> -n <ns> nginx.ingress.kubernetes.io/canary=true nginx.ingress.kubernetes.io/canary-weight="20"
Rate limit and body size annotations
kubectl annotate ingress <name> -n <ns> nginx.ingress.kubernetes.io/limit-rps="10" nginx.ingress.kubernetes.io/proxy-body-size="50m"
Rewrite-target with capture group
kubectl annotate ingress <name> -n <ns> nginx.ingress.kubernetes.io/rewrite-target='/$2' nginx.ingress.kubernetes.io/use-regex='true'
List ingressclasses and default
kubectl get ingressclass -o custom-columns='NAME:.metadata.name,DEFAULT:.metadata.annotations.ingressclass\.kubernetes\.io/is-default-class'
Dump effective nginx config
kubectl exec deploy/ingress-nginx-controller -n ingress-nginx -- nginx -T | less