Technology: ingress-nginx
| ID | Title | Description | Category | Technology | Tags |
|---|---|---|---|---|---|
| prequel-2025-0027 Low Impact: 5/10 Mitigation: 2/10 | Ingress Nginx Prefix Wildcard Error | The 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 Problems | ingress-nginx | NginxIngressKubernetes |
| prequel-2025-0102 High Impact: 7/10 Mitigation: 6/10 | Ingress Nginx HTTP 5XX Error | The ingress-nginx controller is returning HTTP 5XX errors | Ingress Problems | ingress-nginx | NginxIngressErrors |
| prequel-2025-0103 High Impact: 4/10 Mitigation: 5/10 | Ingress Nginx Backend Service Has No Active Endpoints | The ingress-nginx controller has detected that a service does not have any active endpoints. This typically happens when the service selector does not match any pods or the pods are not in a ready state. The controller logs a warning message indicating that the service does not have any active endpoints. | Ingress Problems | ingress-nginx | NginxIngressKubernetesService |
| prequel-2025-0104 Medium Impact: 5/10 Mitigation: 4/10 | Ingress Nginx can't obtain X.509 certificate | The Nginx ingress encountered an error while trying to obtain an X.509 certificate from the Kubernetes secret. | Ingress Problems | ingress-nginx | KubernetesCertificateNginxIngress |