search

kubernetes / ingress-nginx

Ingress NGINX Controller for Kubernetes
https://kubernetes.github.io/ingress-nginx/
Apache License 2.0
17.58k stars 8.27k forks source link

Issues with ingress-nginx controller "Error reading system nameservers: open /etc/resolv.conf" #10743

Closed arunpatchaivy closed 11 months ago

arunpatchaivy commented 11 months ago

we are trying to setup RKE in our local environment. we are currently facing issues with ingress controller.

we have tried upgrading RKE k8s from 1.26 to 1.27 still we are seeing below issue. can some someone suggest us how to fix this issue.

Getting "Error reading system nameservers: open /etc/resolv.conf: permission denied" 6 client_config.go:618] Neither --kubeconfig nor --master was specified. Using the inClusterConfig. This might not work. I1206 13:17:28.646909 6 main.go:209] "Creating API client" host=" https://10.43.0.1:443" I1206 13:17:28.654232 6 main.go:253] "Running in Kubernetes cluster" major="1" minor="26" git="v1.26.8" state="clean" commit="395f0a2fdc940aeb9ab88849e8fa43 21decbf6e1" platform="linux/amd64" I1206 13:17:28.716388 6 main.go:104] "SSL fake certificate created" file="/etc/ingress-controller/ssl/default-fake-certificate.pem" W1206 13:17:28.732087 6 nginx.go:83] Error reading system nameservers: open /etc/resolv.conf: permission denied I1206 13:17:28.734383 6 ssl.go:533] "loading tls certificate" path="/usr/local/certificates/cert" key="/usr/local/certificates/key" I1206 13:17:28.747225 6 nginx.go:261] "Starting NGINX Ingress controller" I1206 13:17:28.763108 6 event.go:285] Event(v1.ObjectReference{Kind:"ConfigMap", Namespace:"ingress-nginx", Name:"ingress-nginx-controller", UID:"0765a2be-0 9da-4a0f-8f91-67c88c0792c3", APIVersion:"v1", ResourceVersion:"1159", FieldPath:""}): type: 'Normal' reason: 'CREATE' ConfigMap ingress-nginx/ingress-nginx-contro ller I1206 13:17:28.766776 6 event.go:285] Event(v1.ObjectReference{Kind:"ConfigMap", Namespace:"ingress-nginx", Name:"tcp-services", UID:"9d22b360-097c-4390-bbd a-e65d47c3232d", APIVersion:"v1", ResourceVersion:"1160", FieldPath:""}): type: 'Normal' reason: 'CREATE' ConfigMap ingress-nginx/tcp-services I1206 13:17:28.766853 6 event.go:285] Event(v1.ObjectReference{Kind:"ConfigMap", Namespace:"ingress-nginx", Name:"udp-services", UID:"9d87056c-6b29-434a-a36 c-4c9340340abc", APIVersion:"v1", ResourceVersion:"1161", FieldPath:""}): type: 'Normal' reason: 'CREATE' ConfigMap ingress-nginx/udp-services I1206 13:17:29.949039 6 nginx.go:304] "Starting NGINX process" I1206 13:17:29.949105 6 leaderelection.go:248] attempting to acquire leader lease ingress-nginx/ingress-controller-leader-nginx... I1206 13:17:29.949501 6 nginx.go:324] "Starting validation webhook" address=":8443" certPath="/usr/local/certificates/cert" keyPath="/usr/local/certificates /key" I1206 13:17:29.949967 6 controller.go:189] "Configuration changes detected, backend reload required" I1206 13:17:29.957123 6 leaderelection.go:258] successfully acquired lease ingress-nginx/ingress-controller-leader-nginx I1206 13:17:29.957178 6 status.go:84] "New leader elected" identity="nginx-ingress-controller-5gcfl" I1206 13:17:29.962009 6 status.go:215] "POD is not ready" pod="ingress-nginx/nginx-ingress-controller-5gcfl" node="preprod.rke.worker.4" I1206 13:17:29.962033 6 status.go:215] "POD is not ready" pod="ingress-nginx/nginx-ingress-controller-8lsvh" node="preprod.rke.worker.2" I1206 13:17:29.962041 6 status.go:215] "POD is not ready" pod="ingress-nginx/nginx-ingress-controller-jdjxt" node="preprod.rke.worker.3" I1206 13:17:29.962046 6 status.go:215] "POD is not ready" pod="ingress-nginx/nginx-ingress-controller-m6k5d" node="preprod.rke.worker.1" I1206 13:17:30.025002 6 controller.go:206] "Backend successfully reloaded" I1206 13:17:30.025076 6 controller.go:217] "Initial sync, sleeping for 1 second" I1206 13:17:30.025171 6 event.go:285] Event(v1.ObjectReference{Kind:"Pod", Namespace:"ingress-nginx", Name:"nginx-ingress-controller-5gcfl", UID:"3eb6bcc6-0 758-4015-a6a1-9dbaba38adc2", APIVersion:"v1", ResourceVersion:"253618", FieldPath:""}): type: 'Normal' reason: 'RELOAD' NGINX reload triggered due to a change in configuration 2023/12/06 13:17:30 [error] 24#24: init_by_lua error: init_by_lua:9: require failed: /etc/nginx/lua/util/resolv_conf.lua:70: could not open /etc/resolv.conf: /etc /resolv.conf: Permission denied ingres-nginx-controller.log

k8s-ci-robot commented 11 months ago

This issue is currently awaiting triage.

If Ingress contributors determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.
longwuyuan commented 11 months ago

I think its best to ask in the Rancher forums or the rancher channel of the Kubernetes slack because we don't test with RKE and also RKE bundles a different build than those released by this project.

/close

k8s-ci-robot commented 11 months ago

@longwuyuan: Closing this issue.

In response to [this](https://github.com/kubernetes/ingress-nginx/issues/10743#issuecomment-1849171693): >I think its best to ask in the Rancher forums or the rancher channel of the Kubernetes slack because we don't test with RKE and also RKE bundles a different build than those released by this project. > >/close Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.