Opened 6 months ago
Closed 6 months ago
#2559 closed defect (invalid)
K8S ingress rule fails to match Exact /
| Reported by: | Owned by: | ||
|---|---|---|---|
| Priority: | minor | Milestone: | |
| Component: | other | Version: | 1.25.x |
| Keywords: | ingress Exact path | Cc: | |
| uname -a: | Linux rke2-ingress-nginx-controller-8tj7j 5.3.18-150300.59.106-default #1 SMP Mon Dec 12 13:16:24 UTC 2022 (774239c) x86_64 x86_64 x86_64 GNU/Linux | ||
| nginx -V: | nginx version: nginx/1.21.4 | ||
Description
Using:
│app.kubernetes.io/name: rke2-ingress-nginx │app.kubernetes.io/version: 1.6.4 │helm.sh/chart: rke2-ingress-nginx-4.5.201
Having an ingress with:
│ rules:
│ - http:
│ paths:
│ - backend:
│ service:
│ name: powerflex-status-ui
│ port:
│ number: 80
│ path: /
│ pathType: Exact
When calling:
curl -k -H 'Cache-Control: no-cache, no-store' -I https://100.68.80.54/
HTTP/2 404
It worked with an older version. We have a workaround, adding $ to the expression.
│ rules:
│ - http:
│ paths:
│ - backend:
│ service:
│ name: powerflex-status-ui
│ port:
│ number: 80
│ path: /$
│ pathType: Exact
That one seems identical but it works - getting http 200
This looks like an issue in the K8S ingress controller you are using, not in nginx. Please consider reporting to the development team of the ingress controller you are using.