Can't include $ in permanent-redirect URL annotation #11175
Labels
kind/bug
Categorizes issue or PR as related to a bug.
lifecycle/frozen
Indicates that an issue or PR should not be auto-closed due to staleness.
priority/backlog
Higher priority than priority/awaiting-more-evidence.
triage/accepted
Indicates an issue or PR is ready to be actively worked on.
triage/needs-information
Indicates an issue needs more information in order to work on it.
What happened:
When attempting to add a
permanent-redirect
annotation with an nginx variable, the admission controller wouldn't allow it.nginx.ingress.kubernetes.io/permanent-redirect: https://redirectedto.com$request_uri
Results in:
admission webhook "validate.nginx.ingress.kubernetes.io" denied the request: annotation nginx.ingress.kubernetes.io/permanent-redirect contains invalid value
What you expected to happen:
In earlier versions this syntax was allowed. I have been using up until recently.
NGINX Ingress controller version (exec into the pod and run nginx-ingress-controller --version.):
Version 1.9.6 installed via helm chart 4.9.1
Kubernetes version (use
kubectl version
):v1.27.11
Environment:
uname -a
): 5.10.0-27-cloud-amd64Please mention how/where was the cluster created like kubeadm/kops/minikube/kind etc.
kubectl version
: v1.27.11kubectl get nodes -o wide
helm ls -A | grep -i ingress
helm -n <ingresscontrollernamespace> get values <helmreleasename>
kubectl describe ingressclasses
kubectl -n <ingresscontrollernamespace> get all -A -o wide
kubectl -n <ingresscontrollernamespace> describe po <ingresscontrollerpodname>
kubectl -n <ingresscontrollernamespace> describe svc <ingresscontrollerservicename>
Please let me know if the rest is needed.
kubectl -n <appnamespace> get all,ing -o wide
kubectl -n <appnamespace> describe ing <ingressname>
This occurs with any ingress.
kubectl describe ...
of any custom configmap(s) created and in useHow to reproduce this issue:
Try to add an ingress that uses
permanent-redirect
with a$
in the URL.Anything else we need to know:
The text was updated successfully, but these errors were encountered: