-
**What happened**:
I enabled the tcp port 8440 in nginx ingress controller deployment and service and try to consume from upstream system using hostname which mapped into ingress load balan…
-
/kind bug
**What steps did you take and what happened:**
When reconciling Security Group ingress rules, CAPA is comparing sets that are not equivalent. That happens because in [this commit](http…
-
**What happened**:
We deployed the `NGINX Ingress controller` dashboard, but because many of our `ingress` objects are named the same over namespaces, we can't get a clear view of each in the dashb…
-
I believe Gateway API was meant to be v2 of Ingress API. Also, as per the [documentation for Gateway API](https://gateway-api.sigs.k8s.io/):
> The Gateway API was originally designed to manage traf…
-
IMAGE SYNC
-
I see in README "nghttpx ingress controller is created based on nginx ingress controller." which makes sense but looking at this repo and knowing it has less people behind it, it makes me wonder: Why …
-
thanks so much for responding. RKE 1 currently uses canal which is combination of flannel and calico https://ubuntu.com/kubernetes/docs/cni-canal
since flannel is part of canal I guess cis should t…
-
**What happened**:
When adding a default backend to the nginx controller when the controller has a namespace defined in scope, I am receiving a 500 internal server error. When removing the namesp…
-
Currently the only supported path type is `Prefix`, which makes sense for simplicity and common use cases.
Unfortunately, a lot of helm charts in the wild assume `nginx-ingress` is being used and h…
diegs updated
1 month ago
-
This is basically #8680 but unlike what we thought at the time, it doesn't seem fixed on newer kernel/Fedora CoreOS/cri-o.
**What happened**:
When starting the controller it errors with …