Looking at the nginx ingress controller code had a question about the design. See that there is a function, getPodsForIngressBackend, ( https://github.com/nginxinc/kubernetes-ingress/blob/master/internal/k8s/controller.go#L15860 ). It looks like in this function a call is made to kube api to grab all the backend pods for a service. I was wondering why not use the cached information from the inby ayma - Nginx Mailing List - English
Hi I'm trying to use ETags with nginx when looking at html data (Content-Type: text/html). I don't see an issue when the content-type comes back as Content-Type: text/plain. To reduce noise I tried the following: I created an nginx conf file on my local host that would serve up an html page and created the ETag header inside server { listen 3000; location / {by ayma - Nginx Mailing List - English