This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(252.8, 9%, 34%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EMF%3C/text%3E%3C/svg%3E)
This one is working fine:
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
name: php-info
annotations:
# Enable ModSecurity and OWASP CRS
nginx.ingress.kubernetes.io/enable-modsecurity: "true"
nginx.ingress.kubernetes.io/enable-owasp-modsecurity-crs: "true"
# nginx.ingress.kubernetes.io/modsecurity-snippet: |-
# SecRuleEngine On
# SecRequestBodyAccess On
# SecAuditLog /dev/stdout
# SecAuditLogFormat JSON
nginx.ingress.kubernetes.io/rewrite-target: /$2
spec:
#ingressClassName: external-nginx
rules:
- http:
paths:
- path: /
pathType: ImplementationSpecific
backend:
service:
name: php-info
port:
number: 8080
But when I change:
- path: /
to
- path: /p
It doesn't work. Even port 80 is not opened. Any idea?
I am browsing using IP address in that case and I would like to browse using IP address.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(265.6, 24%, 35%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EDR%3C/text%3E%3C/svg%3E)
Hi Mariusz Ferdyn,
I understand that where your NGINX ingress works when the path is / but stops working when you change the path to /p, and you're testing via the IP address rather than a hostname.
By default, Ingress rules are host-based and route only if the host and path both match. If you want to access the ingress via its IP address, you need to omit the host: field in the ingress definition. Then the ingress will accept all hosts, including requests made directly to the IP address.
If you want to use the path as /p then use a regex-style path to capture everything after /p by using the rewrite-target URI annotations. The nginx.ingress.kubernetes.io/rewrite-target describes the target URI where the traffic must be redirected.
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
name: php-info
annotations:
nginx.ingress.kubernetes.io/rewrite-target: /$2
spec:
rules:
- http:
paths:
- path: /p(/|$)(.*)
pathType: Prefix
backend:
service:
name: php-info
port:
number: 8080
rewrite-target: /$2: This rewrites the incoming path. With the path rule /p(/|$)(.*), it captures what's after /p and rewrites the request path to only send that part to the backend. Also, you can test your Kubernetes Ingress routing using curl command.
Please check the document about the ingress rules and rewrite-target URI
If you have any further queries, let me know. If the information is helpful, please click on Upvote.
Thank you.
Hi Mariusz Ferdyn,
Just checking in to see if you have got a chance to see my response to your question in resolving the issue.
If it was helpful, please click "Upvote" on this post to let us know.
Thank You.
The problem was with healthchecks. So fix needed in:
service:
annotations:
service.beta.kubernetes.io/azure-load-balancer-health-probe-request-path: /