From 4a913fac2a1e770b5aad362d5b79423afa1d5ac9 Mon Sep 17 00:00:00 2001 From: Nikolas Skoufis Date: Wed, 5 Jun 2019 11:14:50 +1000 Subject: [PATCH] Add clarification on how to enable path matching The fact that you need to explicitly add the annotation is easy to miss. This makes this more explicit, while leaving the finer details to the linked annotations document. --- docs/user-guide/ingress-path-matching.md | 1 + 1 file changed, 1 insertion(+) diff --git a/docs/user-guide/ingress-path-matching.md b/docs/user-guide/ingress-path-matching.md index 6aa1d9c3d..ae1c1b584 100644 --- a/docs/user-guide/ingress-path-matching.md +++ b/docs/user-guide/ingress-path-matching.md @@ -6,6 +6,7 @@ Regular expressions and wild cards are not supported in the `spec.rules.host` field. Full hostnames must be used. The ingress controller supports **case insensitive** regular expressions in the `spec.rules.http.paths.path` field. +This can be enabled by setting the `nginx.ingress.kubernetes.io/use-regex` annotation to `true` (the default is false). See the [description](./nginx-configuration/annotations.md#use-regex) of the `use-regex` annotation for more details.