Connection timed out for controller Pods. #11426
Comments
|
This issue is currently awaiting triage. If Ingress contributors determines this is a relevant issue, they will accept it by applying the The 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-sigs/prow repository. |
k8s-ci-robot
added
needs-triage
|
/remove-kind bug The default install of the controller is not a daemonset. The daemonset use-case and NodePort use-case require advanced awareness. So the info provided also has to be much much much much more granular and wider-scoped than what is asked in a new bug-report template. So try a default install without any custom values file and post the data from that. Next use a vlaues file of your liking or what you posted and then paste data from that. |
k8s-ci-robot
added
kind/support
|
This is stale, but we won't close it automatically, just bare in mind the maintainers may be busy with other tasks and will reach your issue ASAP. If you have any question or request to prioritize this, please reach |
github-actions
bot
added
the
lifecycle/frozen
What happened:
After installing the Ingress-Nginx, it's Pods timeout.
NGINX Ingress controller version:
Kubernetes version:
Environment:
bare-metaluname -a):$ uname -a Linux master-1 5.15.0-107-generic #117-Ubuntu SMP Fri Apr 26 12:26:49 UTC 2024 x86_64 x86_64 x86_64 GNU/Linuxkubeadm$ helm ls -A | grep -i ingress ingress-nginx ingress-nginx 1 2024-06-05 09:25:13.228270574 +0000 UTC deployed ingress-nginx-4.10.1 1.10.1$ helm -n ingress-nginx get values ingress-nginx USER-SUPPLIED VALUES: controller: kind: DaemonSet metrics: enabled: true service: nodePorts: http: 32080 https: 32443 ports: http: 80 https: 443 targetPorts: http: http https: https type: NodePort$ kubectl describe ingressclasses Name: nginx Labels: app.kubernetes.io/component=controller app.kubernetes.io/instance=ingress-nginx app.kubernetes.io/managed-by=Helm app.kubernetes.io/name=ingress-nginx app.kubernetes.io/part-of=ingress-nginx app.kubernetes.io/version=1.10.1 helm.sh/chart=ingress-nginx-4.10.1 Annotations: meta.helm.sh/release-name: ingress-nginx meta.helm.sh/release-namespace: ingress-nginx Controller: k8s.io/ingress-nginx Events: <none>$ kubectl -n ingress-nginx describe pod/ingress-nginx-controller-dd5g9 Name: ingress-nginx-controller-dd5g9 Namespace: ingress-nginx Priority: 0 Service Account: ingress-nginx Node: worker-1/10.0.10.36 Start Time: Wed, 05 Jun 2024 09:25:17 +0000 Labels: app.kubernetes.io/component=controller app.kubernetes.io/instance=ingress-nginx app.kubernetes.io/managed-by=Helm app.kubernetes.io/name=ingress-nginx app.kubernetes.io/part-of=ingress-nginx app.kubernetes.io/version=1.10.1 controller-revision-hash=74798dbdc7 helm.sh/chart=ingress-nginx-4.10.1 pod-template-generation=1 Annotations: cni.projectcalico.org/containerID: 2befd8908088683891fe814873bb1d217d2cc41c8d73bcd2486c5e4a43ae5337 cni.projectcalico.org/podIP: 192.168.226.78/32 cni.projectcalico.org/podIPs: 192.168.226.78/32 Status: Running IP: 192.168.226.78 IPs: IP: 192.168.226.78 Controlled By: DaemonSet/ingress-nginx-controller Containers: controller: Container ID: containerd://596956676e18cb14b89f383a21aeba864ddb5d93eb9912ad0b8c89be19c11d78 Image: registry.k8s.io/ingress-nginx/controller:v1.10.1@sha256:e24f39d3eed6bcc239a56f20098878845f62baa34b9f2be2fd2c38ce9fb0f29e Image ID: registry.k8s.io/ingress-nginx/controller@sha256:e24f39d3eed6bcc239a56f20098878845f62baa34b9f2be2fd2c38ce9fb0f29e Ports: 80/TCP, 443/TCP, 10254/TCP, 8443/TCP Host Ports: 0/TCP, 0/TCP, 0/TCP, 0/TCP SeccompProfile: RuntimeDefault Args: /nginx-ingress-controller --publish-service=$(POD_NAMESPACE)/ingress-nginx-controller --election-id=ingress-nginx-leader --controller-class=k8s.io/ingress-nginx --ingress-class=nginx --configmap=$(POD_NAMESPACE)/ingress-nginx-controller --validating-webhook=:8443 --validating-webhook-certificate=/usr/local/certificates/cert --validating-webhook-key=/usr/local/certificates/key State: Running Started: Wed, 05 Jun 2024 09:33:45 +0000 Last State: Terminated Reason: Unknown Exit Code: 255 Started: Wed, 05 Jun 2024 09:25:17 +0000 Finished: Wed, 05 Jun 2024 09:32:51 +0000 Ready: True Restart Count: 1 Requests: cpu: 100m memory: 90Mi Liveness: http-get http://:10254/healthz delay=10s timeout=1s period=10s #success=1 #failure=5 Readiness: http-get http://:10254/healthz delay=10s timeout=1s period=10s #success=1 #failure=3 Environment: POD_NAME: ingress-nginx-controller-dd5g9 (v1:metadata.name) POD_NAMESPACE: ingress-nginx (v1:metadata.namespace) LD_PRELOAD: /usr/local/lib/libmimalloc.so Mounts: /usr/local/certificates/ from webhook-cert (ro) /var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-km2hj (ro) Conditions: Type Status PodReadyToStartContainers True Initialized True Ready True ContainersReady True PodScheduled True Volumes: webhook-cert: Type: Secret (a volume populated by a Secret) SecretName: ingress-nginx-admission Optional: false kube-api-access-km2hj: Type: Projected (a volume that contains injected data from multiple sources) TokenExpirationSeconds: 3607 ConfigMapName: kube-root-ca.crt ConfigMapOptional: <nil> DownwardAPI: true QoS Class: Burstable Node-Selectors: kubernetes.io/os=linux Tolerations: node.kubernetes.io/disk-pressure:NoSchedule op=Exists node.kubernetes.io/memory-pressure:NoSchedule op=Exists node.kubernetes.io/not-ready:NoExecute op=Exists node.kubernetes.io/pid-pressure:NoSchedule op=Exists node.kubernetes.io/unreachable:NoExecute op=Exists node.kubernetes.io/unschedulable:NoSchedule op=Exists Events: Type Reason Age From Message ---- ------ ---- ---- ------- Normal Scheduled 22m default-scheduler Successfully assigned ingress-nginx/ingress-nginx-controller-dd5g9 to worker-1 Normal Pulled 22m kubelet Container image "registry.k8s.io/ingress-nginx/controller:v1.10.1@sha256:e24f39d3eed6bcc239a56f20098878845f62baa34b9f2be2fd2c38ce9fb0f29e" already present on machine Normal Created 22m kubelet Created container controller Normal Started 22m kubelet Started container controller Normal RELOAD 22m nginx-ingress-controller NGINX reload triggered due to a change in configuration Normal SandboxChanged 14m (x2 over 14m) kubelet Pod sandbox changed, it will be killed and re-created. Normal Pulled 14m kubelet Container image "registry.k8s.io/ingress-nginx/controller:v1.10.1@sha256:e24f39d3eed6bcc239a56f20098878845f62baa34b9f2be2fd2c38ce9fb0f29e" already present on machine Normal Created 14m kubelet Created container controller Normal Started 14m kubelet Started container controller Warning Unhealthy 13m (x2 over 14m) kubelet Liveness probe failed: Get "http://192.168.226.78:10254/healthz": dial tcp 192.168.226.78:10254: connect: connection refused Warning Unhealthy 13m (x2 over 14m) kubelet Readiness probe failed: Get "http://192.168.226.78:10254/healthz": dial tcp 192.168.226.78:10254: connect: connection refused Normal RELOAD 13m nginx-ingress-controller NGINX reload triggered due to a change in configuration$ kubectl -n ingress-nginx describe service/ingress-nginx-controller Name: ingress-nginx-controller Namespace: ingress-nginx Labels: app.kubernetes.io/component=controller app.kubernetes.io/instance=ingress-nginx app.kubernetes.io/managed-by=Helm app.kubernetes.io/name=ingress-nginx app.kubernetes.io/part-of=ingress-nginx app.kubernetes.io/version=1.10.1 helm.sh/chart=ingress-nginx-4.10.1 Annotations: meta.helm.sh/release-name: ingress-nginx meta.helm.sh/release-namespace: ingress-nginx Selector: app.kubernetes.io/component=controller,app.kubernetes.io/instance=ingress-nginx,app.kubernetes.io/name=ingress-nginx Type: NodePort IP Family Policy: SingleStack IP Families: IPv4 IP: 10.98.62.6 IPs: 10.98.62.6 Port: http 80/TCP TargetPort: http/TCP NodePort: http 32080/TCP Endpoints: 192.168.133.213:80,192.168.226.78:80,192.168.97.203:80 Port: https 443/TCP TargetPort: https/TCP NodePort: https 32443/TCP Endpoints: 192.168.133.213:443,192.168.226.78:443,192.168.97.203:443 Session Affinity: None External Traffic Policy: Cluster Events: <none>The current state seems fine.
The problem is now that it should be responsible for those NodePorts. but with the first request, it works, and for the other request, it doesn't.:
How to reproduce this issue:
Install the ingress controller
helm install --create-namespace ingress-nginx -n ingress-nginx -f ~/nginx-values.yaml ./ingress-nginx/charts/ingress-nginxAnything else we need to know:
Here are the endpoints as well:
$ kubectl -n ingress-nginx describe ep/ingress-nginx-controller Name: ingress-nginx-controller Namespace: ingress-nginx Labels: app.kubernetes.io/component=controller app.kubernetes.io/instance=ingress-nginx app.kubernetes.io/managed-by=Helm app.kubernetes.io/name=ingress-nginx app.kubernetes.io/part-of=ingress-nginx app.kubernetes.io/version=1.10.1 helm.sh/chart=ingress-nginx-4.10.1 Annotations: endpoints.kubernetes.io/last-change-trigger-time: 2024-06-05T09:50:36Z Subsets: Addresses: 192.168.133.215,192.168.226.81,192.168.97.205 NotReadyAddresses: <none> Ports: Name Port Protocol ---- ---- -------- https 443 TCP http 80 TCP Events: <none>As you see, the endpoints are correct.
The text was updated successfully, but these errors were encountered: