jrhunger

Maybe this was fixed in the latest version. Below is an example of the failure with 21.04.0 and k8s 1.21.9 (although since the error comes from trident-main i would guess...

Looks like this happens for any Role or ClusterRole that has capital letters in its name. Seems the name of the CRD is subject to one of the DNS-like object...

I am having this issue on a server and i think that the error message is misleading. [IsPortAvailable](https://github.com/kubernetes/ingress-nginx/blob/af745bd97dce317a8788589588ae754711df69af/internal/net/net.go#L31) checks if it's possible to bind on the port. if that is...

Looks like in the v1.2.0 image: k8s.gcr.io/ingress-nginx/controller:v1.2.0@sha256:d8196e3bc1e72547c5dec66d6556c0ff92a23f6d0919b206be170bc90d5f9185 that the /nginx-ingress-controller does not have the cap_net_bind_service capability applied, whereas it is on v1.3.0, v1.4.0, and v1.1.3 do. Tested by creating pod...

Leaving the above comment in case it helps someone else in troubleshooting, but in fact when i run the v1.2.0 image on a working node, i *do* see the cap_net_bind_service=ep...

@longwuyuan correct, the v1.2.0 image has the proper cap_net_bind_service when freshly pulled.

@strongjz can you have a look at https://github.com/jrhunger/ingress-nginx/blob/troubleshooting-docs-update-ports/docs/troubleshooting.md#unable-to-listen-on-port-80443 and let me know if that is the kind of thing you are looking for?

@chen-keinan Thank you for trying. This project moves quickly. When i opened this issue we had just tested it on the latest available 0.1.9. Let me try it on 0.3.0...

I have been able to replicate this now on AKS 1.23.8 as well as our on-prem kubeadm-generated 1.23.5 and 1.24.3. I enabled logDevMode but haven't found anything relevant in the...

@chen-keinan as the reporter of #149 can you clarify what you are asking for there? Is that issue asking for the option to disable the creation of a VulnerabilityReport if...