-
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
open() "/etc/ingress-controller/auth/monitoring-dashboard.passwd" failed (13: Permission denied) #210
Comments
Slightly OT, but please add an example for this in: https://github.com/kubernetes/ingress/tree/master/examples if you have the time. I'll need to debug to give more meaningful help, maybe @aledbf knows off the top of his head |
@webwurst are you mounting the |
I am using this configuration https://github.com/codeformuenster/kubernetes-deployment/blob/master/manifests/ingress/daemonset.yaml which is the same as the
|
I can confirm that 0.9.0-beta.1 is currently broken, whereas basic auth with 0.8.3 works well. In both cases I used the following template to create the ingress controller: https://github.com/kubernetes/ingress/blob/3a37607138e3bbdb83dd393241d1fdd3a6232176/examples/deployment/nginx/kubeadm/nginx-ingress-controller.yaml |
https://github.com/kubernetes/ingress/blob/master/core/pkg/ingress/annotations/auth/main.go#L62 Pretty sure this TODO needs to be completed. The /etc/ingress-controller has owner root:root and permissions 0750. The nginx user/worker user ( |
Hi guys, when this fix will be available in new images ? |
Thanks, am I understand correctly that I can use |
@Hronom Yes, |
@evgf Yeah, already switched, thanks |
This seems to work well with the newly released 0.9.0-beta.2 |
I am testing kubeadm/nginx-ingress-controller.yaml with
gcr.io/google_containers/nginx-ingress-controller:0.9.0-beta.1
.Using annotations to configure basic-auth seems to be broken:
The following error shows up:
Here the access rights for that specific file:
When setting
chmod o+rx /etc
this works fine. But not sure if this is a proper fix..The text was updated successfully, but these errors were encountered: