-
**What happened**:
```
service/ingress-nginx-controller-admission created
Warning: spec.template.spec.containers[0].ports[1]: duplicate port definition with spec.template.spec.containers[…
luarx updated
4 weeks ago
-
### Describe the bug:
When setting up server annotations and headers for serving content using nginx-ingress:
**The ZAP Proxy marks this configuration as a vulnerability with a Medium Risk Level a…
-
-
**What happened**:
I am using `nginx.ingress.kubernetes.io/configuration-snippet` together with
`nginx.ingress.kubernetes.io/cors-allow-origin` and `nginx.ingress.kubernetes.io/enable-cors` annota…
fiksn updated
3 weeks ago
-
### What Happened?
* ingress is an addon maintained by Kubernetes. For any concerns contact minikube on GitHub.
You can view the list of minikube maintainers at: https://github.com/kubernetes/miniku…
-
### Bug Description
The change introduced in https://github.com/canonical/tls-certificates-interface/pull/188 is backward incompatible. When a secret created by an earlier version of the library expi…
-
### OAuth2-Proxy Version
7.6.0
### Provider
oidc
### Current Behaviour of your Problem
When the proxy and ingress are configured as below, I get all x-auth header correctly except for t…
-
We are experiencing significant memory issues after upgrading to the ingress-nginx Helm chart version 4.11.2. The memory usage has increased substantially, leading to performance degradation and i…
-
{
"platform":"",
"hub-mirror": [
"registry.k8s.io/ingress-nginx/controller:v1.11.2"
]
}
-
Problem
We are facing an issue where our backend service, behind an Nginx Ingress Controller, occasionally starts returning HTTP 500 errors. When this happens, we notice that our Nginx Ingress Contro…