Skip to main content

Category: Ingress Problems

Problems related to Ingress

IDTitleDescriptionCategoryTechnologyTags
prequel-2025-0027
Low
Impact: 5/10
Mitigation: 2/10
Ingress Nginx Prefix Wildcard ErrorThe NGINX Ingress Controller rejects an Ingress manifest whose `pathType: Prefix` value contains a wildcard (`*`). Log excerpt: ``` ingress: default/api prefix path shouldn't contain wildcards ``` When the controller refuses the rule, it omits it from the generated `nginx.conf`; clients receive **404 / 502** responses even though the manifest was accepted by the Kubernetes API server. The problem appears most often after upgrading to ingress-nginx ≥ 1.8, where stricter validation was added.Ingress Problemsingress-nginxNginxIngressKubernetes