Open gramulka opened 10 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.
What happened:
We're not using enable-topology-aware-routing flag, and cluster access is disabled for us, and on startup nginx gives us the following warning: "W1121 08:47:25.273958 7 main.go:125] Unable to get NODE information: nodes "....internal" is forbidden: User "..." cannot get resource "nodes" in API group "" at the cluster scope"
What you expected to happen:
As enable-topology-aware-routing is disabled by default, we're expecting that nginx wouldn't try to fetch node labels.
NGINX Ingress controller version (exec into the pod and run nginx-ingress-controller --version.):
nginx controller version: 1.8.4
Kubernetes version (use
kubectl version
): 1.26Environment:
Cloud provider or hardware configuration:
OS (e.g. from /etc/os-release):
Kernel (e.g.
uname -a
):Install tools:
Please mention how/where was the cluster created like kubeadm/kops/minikube/kind etc.
Basic cluster related info:
kubectl version
kubectl get nodes -o wide
How was the ingress-nginx-controller installed:
helm ls -A | grep -i ingress
helm -n <ingresscontrollernamepspace> get values <helmreleasename>
Current State of the controller:
kubectl describe ingressclasses
kubectl -n <ingresscontrollernamespace> get all -A -o wide
kubectl -n <ingresscontrollernamespace> describe po <ingresscontrollerpodname>
kubectl -n <ingresscontrollernamespace> describe svc <ingresscontrollerservicename>
Current state of ingress object, if applicable:
kubectl -n <appnnamespace> get all,ing -o wide
kubectl -n <appnamespace> describe ing <ingressname>
Others:
kubectl describe ...
of any custom configmap(s) created and in useHow to reproduce this issue:
Anything else we need to know: