Description
What happened:
I tried to use a new feature to set custom headers per ingress. After setting the annotation the configuration does not apply automatically. While there are sync events in the logs, the config reload is not triggered and nginx.conf is not changed. The feature itself is working if I restart the nginx controller. Also it's working if I set incorrect path to the configmap and then change it back to the correct path.
The update of the applied headers also does not work. If I change the configmap and then delete and add the annotation again, the headers are not changing. I also tried to create a new configmap and change the annotation to point to it, but it does not trigger config reload. Basically the only way to apply the configuration of the custom headers is to either reload the controller or to trigger an errror and then apply working configuration again.
What you expected to happen:
custom-headers annotation changes (add, edit, delete) should trigger the config reload.
Ideally custom headers configuartion should be also updated when the configmap with headers changes, but it's probably not possible
NGINX Ingress controller version:
NGINX Ingress controller
Release: v1.11.1
Build: 7c44f99
Repository: https://github.com/kubernetes/ingress-nginx
nginx version: nginx/1.25.5
Kubernetes version:
v1.27.15-eks-db838b0
Environment:
AWS EKS
Configuration:
allow-snippet-annotations: "false"
global-allowed-response-headers: Referrer-Policy,Strict-Transport-Security,X-Content-Type-Options,X-Frame-Options,Content-Security-Policy
http2-max-field-size: 512k
http2-max-header-size: 512k
large-client-header-buffers: 8 512k
use-proxy-protocol: "true"
Metadata
Metadata
Assignees
Labels
Type
Projects
Status