It's a problem with a k8s component called "Ingress Nginx" (the ingress controller that uses Nginx).

Nginx isn't the problem, but I don't think you can really get away from including it in the title given the name of the component

it's not core k8s either, it's "ingress-nginx", a community maintained implementation of k8s ingresses using nginx as the underlying proxy, (which is different from the nginx / f5 version called nginx-ingress....).