-
Notifications
You must be signed in to change notification settings - Fork 8.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
custom-headers annotation doesn't work as expected #12287
Comments
This issue is currently awaiting triage. If Ingress contributors determines this is a relevant issue, they will accept it by applying the The Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
/remove-kind bug I don't see there is a bug here.
/close |
@longwuyuan: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
@satyamz Thanks in advance for fixing docs. If you can additionally avoid names like "custom-headers" for the configMap (and also address other such aesthetics, if any required), it could be an improvement as well. Secondly, kindly review the e2e-tests for this and see if they can be improved too (cosmetic and otherwise). Regards |
duplicate of #11339 |
What happened:
I have been trying to have custom response headers via annotation:
nginx.ingress.kubernetes.io/custom-headers
however, ingress endpoint is returning503
. Please find the relevant information below:Ingress spec:
ConfigMap:
Ingress controller configMap:
Ingress controller logs:
Specific log to notice in the above:
Curl to the endpoint:
What you expected to happen:
custom response headers should have been added to the response but application is failing and its returning 503.
NGINX Ingress controller version (exec into the pod and run nginx-ingress-controller --version.):
v1.11.2
Kubernetes version (use
kubectl version
):Tested on both 1.25 and 1.30
Environment:
EKS and minikube
uname -a
):Please mention how/where was the cluster created like kubeadm/kops/minikube/kind etc.
minikube and managed EKS.
kubectl version
kubectl get nodes -o wide
How was the ingress-nginx-controller installed:
helm ls -A | grep -i ingress
helm -n <ingresscontrollernamespace> get values <helmreleasename>
minikube addon enable ingress
Current State of the controller:
kubectl describe ingressclasses
kubectl -n <ingresscontrollernamespace> get all -A -o wide
kubectl -n <ingresscontrollernamespace> describe po <ingresscontrollerpodname>
kubectl -n <ingresscontrollernamespace> describe svc <ingresscontrollerservicename>
Current state of ingress object, if applicable:
kubectl -n <appnamespace> get all,ing -o wide
kubectl -n <appnamespace> describe ing <ingressname>
Others:
kubectl describe ...
of any custom configmap(s) created and in useHow to reproduce this issue:
You can reproduce this issue in following steps:
global-allowed-response-headers
with relevant header keys to ingress controller configMap.custom-headers-map
containing headers in the same namespace as of ingress object.nginx.ingress.kubernetes.io/custom-headers: custom-headers-map
Anything else we need to know:
This issue is happening across all environments (Minikube, EKS, self hosted Kuberentes clusters). I tested it on 1.12 beta version of the ingress controller too.
The text was updated successfully, but these errors were encountered: