-
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
Error reading BasicDigestAuth annotation #3493
Comments
This could be related to the helm, because I could not reproduce the issue using minikube and the yaml file (see below): Minikube: v0.31.0 Secret in the "kube-public" namespace:
Ingress can be created in the the namespace "ns01" and reference the secret from other namespace:
my yaml file:
|
I am experiencing this same failure with ingress-nginx 0.22.0. Looks to me like this code is not properly recognizing the namespace/name format of the auth-secret annotation. |
I'm having the same problem with 0.22.0
|
same on |
1 similar comment
same on |
/reopen |
@zeph: You can't reopen an issue/PR unless you authored it or you are a collaborator. 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/test-infra repository. |
@andrewnazarov could u? I mean, this is a regression... if it was expected to work |
BUG REPORT
NGINX Ingress controller version:
0.20.0
Kubernetes version (use
kubectl version
):v1.10.6-gke.11
Environment:
uname -a
):What happened:
I'm getting the following error
E1130 02:45:08.134955 9 annotations.go:177] error reading BasicDigestAuth annotation in Ingress review/dbs-ingress: unexpected error reading secret review/kube-public/basic-auth-db: no object matching key "review/kube-public/basic-auth-db" in local store
when I want to use a secret from a different namespace. The namespace of the ingress resource is appended to the object's path ('review' is the namespace).
What you expected to happen:
kube-public/basic-auth-db secret is taken by the ingress controller as stated here.
How to reproduce it (as minimally and precisely as possible):
annotate your ingress resource with
nginx.ingress.kubernetes.io/auth-secret: kube-public/basic-auth-db
and deploy it to a namespace different from kube-public.
The text was updated successfully, but these errors were encountered: