You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 17, 2019. It is now read-only.
Hello,
When upgrading the NGINX Ingress Controller image from v. 0.8.3 to v. 0.9.0-beta.1 (gcr.io/google_containers/nginx-ingress-controller:0.9.0-beta.1) we discovered that all our Ingresses using basic authentication do not work (HTTP 500).
The reason is that the auth data are stored in /etc/ingress-controller/auth but the privileges of the /etc directory were changed from 755 (in 0.8.3) to 750 (in 0.9.0 beta 1). The NGINX worker processes run as nobody and cannot open these files:
It seems that some work was invested into moving the NGINX-specific files under /ingress-controller but this does not cover the auth data and the new directory also has the 750 privileges.
The text was updated successfully, but these errors were encountered:
Thank you @aledbf!
Do you know when the new image will be available?
docker pull gcr.io/google_containers/nginx-ingress-controller:0.9.0-beta.2
Pulling
repository gcr.io/google_containers/nginx-ingress-controller
Tag 0.9.0-beta.2 not found in repository gcr.io/google_containers/nginx-ingress-controller
Hello,
When upgrading the NGINX Ingress Controller image from v. 0.8.3 to v. 0.9.0-beta.1 (gcr.io/google_containers/nginx-ingress-controller:0.9.0-beta.1) we discovered that all our Ingresses using basic authentication do not work (HTTP 500).
The reason is that the auth data are stored in /etc/ingress-controller/auth but the privileges of the /etc directory were changed from 755 (in 0.8.3) to 750 (in 0.9.0 beta 1). The NGINX worker processes run as nobody and cannot open these files:
It seems that some work was invested into moving the NGINX-specific files under /ingress-controller but this does not cover the auth data and the new directory also has the 750 privileges.
The text was updated successfully, but these errors were encountered: