-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
4.12 breaks my application - possibly allowSnippetAnnotations: true? #12821
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. |
will revert the upgrade now while filling out version to unblock my team / not keep the application broken for too long |
You need to increase the maximum allowed annotation risk level to |
i see - can we also document this in https://kubernetes.github.io/ingress-nginx/user-guide/nginx-configuration/configmap/#allow-snippet-annotations and add this as a breaking change to the release notes? I guess this is marked with an ⚠ in the changelog but its hard to know the implications: |
There's documentation about annotations and their risk level: https://kubernetes.github.io/ingress-nginx/user-guide/nginx-configuration/annotations-risk/ |
What happened:
After upgrade, microservices no longer get requests, instead theyre forwarded to another ingress with wildcard
Requests are handles by this ingress apparently:
What you expected to happen:
requests to /api/userservice goes to ingress with /api/userservice, not to ingress with /
request should be handled by this ingress ( path: /userservice/api):
NGINX Ingress controller version (exec into the pod and run
/nginx-ingress-controller --version
):Kubernetes version (use
kubectl version
):Environment:
uname -a
): Linux nginx-ingress-nginx-controller-6fcd4674d9-kbpnh 5.15.0-1075-azure Detailed NGINX-Ingress-Controller status page config #84-Ubuntu SMP Mon Oct 21 15:42:52 UTC 2024 x86_64 LinuxPlease mention how/where was the cluster created like kubeadm/kops/minikube/kind etc.
azure uikubectl version
kubectl get nodes -o wide
helm ls -A | grep -i ingress
nginx ingress 50 2025-02-12 09:35:40.808695632 +0000 UTC deployed ingress-nginx-4.12.0 1.12.0helm -n <ingresscontrollernamespace> get values <helmreleasename>
If helm was not used, then copy/paste the complete precise command used to install the controller, along with the flags and options used
if you have more than one instance of the ingress-nginx-controller installed in the same cluster, please provide details for all the instances
Current State of the controller:
kubectl describe ingressclasses
kubectl -n <ingresscontrollernamespace> get all -A -o wide
-A is all namespaces, that is way too much output
kubectl -n <ingresscontrollernamespace> describe po <ingresscontrollerpodname>
kubectl -n <ingresscontrollernamespace> describe svc <ingresscontrollerservicename>
kubectl -n <appnamespace> get all,ing -o wide
all is again too much output, ing is manageable
kubectl -n <appnamespace> describe ing <ingressname>
Responds with HTML from objego-client instead of JSON from objego-user-service:
kubectl describe ...
of any custom configmap(s) created and in useHow to reproduce this issue:
Anything else we need to know:
The text was updated successfully, but these errors were encountered: