Comment on Critical Unauthenticated Remote Code Execution Vulnerabilities in Ingress NGINXComments−boxed1yDid I read this right that it's a problem with k8s, and not nginx? Seems not very nice to have nginx in the title, when it's not the problem.−yoru-sulfur1yIt'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−arccy1yit'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....).
Comments
Did I read this right that it's a problem with k8s, and not nginx? Seems not very nice to have nginx in the title, when it's not the problem.
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....).