-
Notifications
You must be signed in to change notification settings - Fork 8.2k
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
nginx ingress controller fails when -watch-namespace FLAG added to controller #5758
Comments
I don't see the error |
Not sure how you installed the ingress controller but you need to make sure you can get namespaces |
Hi, $ kubectl get all -n ingress-nginx NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE NAME READY UP-TO-DATE AVAILABLE AGE NAME DESIRED CURRENT READY AGE NAME COMPLETIONS DURATION AGE Now the Pod Error: $ kubectl logs ingress-nginx-controller1-59d755cf4f-rkxt5 -n ingress-nginxNGINX Ingress controller I0623 14:16:13.407648 6 flags.go:204] Watching for Ingress class: nginx1 Regards |
Hello, I ran into a similar problem a while back and found a workaround for the issue. In my situation, my cluster was provisioned on GKE with Kubernetes version 1.14.10 and we wanted to use the nginx ingress controller in limited namespaces. This was a public cluster. I downloaded the file indicated in the install instructions Then I made 2 additions to get things working: Here is my file, but note that it is a few versions out of date:
Hope this can help others! |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
Stale issues rot after 30d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
Rotten issues close after 30d of inactivity. Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
@fejta-bot: Closing this issue. 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. |
@rangapv the static yaml manifests require additional roles if you use the If you use helm, it creates that for you The equivalent for the manifest you used:
|
NGINX Ingress controller version: NGINX Ingress controller Release:0.32.0
Kubernetes version (use
kubectl version
):$ kubectl version
Client Version: version.Info{Major:"1", Minor:"18", GitVersion:"v1.18.3", GitCommit:"2e7996e3e2712684bc73f0dec0200d64eec7fe40", GitTreeState:"clean", BuildDate:"2020-05-20T12:52:00Z", GoVersion:"go1.13.9", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"18", GitVersion:"v1.18.0", GitCommit:"9e991415386e4cf155a24b1da15becaa390438d8", GitTreeState:"clean", BuildDate:"2020-03-25T14:50:46Z", GoVersion:"go1.13.8", Compiler:"gc", Platform:"linux/amd64"}
Environment:
NAME="Ubuntu"
VERSION="16.04.6 LTS (Xenial Xerus)"
ID=ubuntu
uname -a
): Linux kubenode20 4.15.0-1077-gcp [Feature Request] Allow for multiple hosts #87~16.04.1-Ubuntu SMP Sat Jun 6 01:51:20 UTC 2020 x86_64 x86_64 x86_64 GNU/LinuxWhat happened: Installing Multiple Ingress Controllers on the same cluster . Both controllers are from nginx. They work perfectly fine when ingress-class is mentioned . But when "--watch-namespace" FLAG is added to the container in the Deployment manifest, the container crasshloops and never starts. The error message is posted above . It complains about not able to have access to API.
What you expected to happen:
The nginx ingress controller should start and be in running state
No Clue!
How to reproduce it:
Anything else we need to know:
The Ingress controller works perfectly fine when the watch-namespace flag is removed
/kind bug
The text was updated successfully, but these errors were encountered: