https://rancher.com/ logo
Join Slack
Powered by
This message was deleted.
# k3s
a
This message was deleted.
t
Copy code
$ kubectl -n kube-system get ds svclb-ingress-nginx-controller-10b72095
NAME                                      DESIRED   CURRENT   READY   UP-TO-DATE   AVAILABLE   NODE SELECTOR   AGE
svclb-ingress-nginx-controller-10b72095   5         5         5       5            5           <none>          120d

$ kubectl -n ingress-system get svc
NAME                               TYPE           CLUSTER-IP      EXTERNAL-IP                                                                  PORT(S)                      AGE
ingress-nginx-controller           LoadBalancer   10.43.25.104    100.115.34.57,100.117.195.128,100.126.100.42,100.126.241.86,100.66.168.143   80:30339/TCP,443:31202/TCP   120d
ingress-nginx-controller-metrics   ClusterIP      10.43.248.77    <none>                                                                       10254/TCP                    120d
ingress-nginx-defaultbackend       ClusterIP      10.43.143.122   <none>                                                                       80/TCP                       120d

$ while true; do curl --write-out '%{http_code}' --silent --output /dev/null <http://argo-cd.home.portefaix.xyz> ; echo ;  ; done
502
502
502
000
502
502
502
200
200
502
000
200
200
Copy code
ingress-nginx-controller-b88sj controller 2023/12/28 09:11:17 [error] 201#201: *885287 recv() failed (104: Connection reset by peer) while reading response header from upstream, client: 10.0.1.77, server: <http://argo-cd.home.portefaix.xyz|argo-cd.home.portefaix.xyz>, request: " GET  / HTTP/1.1", upstream: "<http://10.0.1.249:8080/>", host: "<http://argo-cd.home.portefaix.xyz|argo-cd.home.portefaix.xyz>"
ingress-nginx-controller-b88sj controller {"time": "2023-12-28T09:11:17+01:00", "remote_addr": "", "x_forwarded_for": "10.0.1.77", "request_id": "74564a584453821473b24b3f671e852c", "remote_user": "", "bytes_sent": 6598, "request_time": 0.626, "status": 502, "vhost": "<http://argo-cd.home.portefaix.xyz|argo-cd.home.portefaix.xyz>", "request_proto": "HTTP/1.1", "path": "/", "request_query": "", "request_length": 89, "duration": 0.626,"method": " GET ", "http_referrer": "", "http_user_agent": "curl/8.4.0"} #magic___^_^___line
ingress-nginx-controller-lcxrb controller 2023/12/28 09:11:17 [error] 5648#5648: *865437 recv() failed (104: Connection reset by peer) while reading response header from upstream, client: 10.0.1.77, server: <http://argo-cd.home.portefaix.xyz|argo-cd.home.portefaix.xyz>, request: " GET  / HTTP/1.1", upstream: "<http://10.0.1.249:8080/>", host: "<http://argo-cd.home.portefaix.xyz|argo-cd.home.portefaix.xyz>"
ingress-nginx-controller-lcxrb controller 2023/12/28 09:11:17 [error] 5648#5648: *865437 recv() failed (104: Connection reset by peer) while reading response header from upstream, client: 10.0.1.77, server: <http://argo-cd.home.portefaix.xyz|argo-cd.home.portefaix.xyz>, request: " GET  / HTTP/1.1", upstream: "<http://10.0.1.249:8080/>", host: "<http://argo-cd.home.portefaix.xyz|argo-cd.home.portefaix.xyz>"
ingress-nginx-controller-lcxrb controller 2023/12/28 09:11:17 [error] 5648#5648: *865437 recv() failed (104: Connection reset by peer) while reading response header from upstream, client: 10.0.1.77, server: <http://argo-cd.home.portefaix.xyz|argo-cd.home.portefaix.xyz>, request: " GET  / HTTP/1.1", upstream: "<http://10.0.1.249:8080/>", host: "<http://argo-cd.home.portefaix.xyz|argo-cd.home.portefaix.xyz>"
ingress-nginx-controller-lcxrb controller {"time": "2023-12-28T09:11:17+01:00", "remote_addr": "", "x_forwarded_for": "10.0.1.77", "request_id": "f455c15c7c0ab68052a8168ee7a3eb0e", "remote_user": "", "bytes_sent": 6598, "request_time": 0.634, "status": 502, "vhost": "<http://argo-cd.home.portefaix.xyz|argo-cd.home.portefaix.xyz>", "request_proto": "HTTP/1.1", "path": "/", "request_query": "", "request_length": 89, "duration": 0.634,"method": " GET ", "http_referrer": "", "http_user_agent": "curl/8.4.0"} #magic___^_^___line
ingress-nginx-controller-k794d controller {"time": "2023-12-28T09:11:17+01:00", "remote_addr": "", "x_forwarded_for": "192.168.0.62", "request_id": "1393016541b3fc4b16ebe61a7124793c", "remote_user": "", "bytes_sent": 1074, "request_time": 0.001, "status": 200, "vhost": "<http://argo-cd.home.portefaix.xyz|argo-cd.home.portefaix.xyz>", "request_proto": "HTTP/1.1", "path": "/", "request_query": "", "request_length": 89, "duration": 0.001,"method": " GET ", "http_referrer": "", "http_user_agent": "curl/8.4.0"} #magic___^_^___line
ingress-nginx-controller-lcxrb controller 2023/12/28 09:11:18 [error] 5648#5648: *865455 recv() failed (104: Connection reset by peer) while reading response header from upstream, client: 10.0.1.77, server: <http://argo-cd.home.portefaix.xyz|argo-cd.home.portefaix.xyz>, request: " GET  / HTTP/1.1", upstream: "<http://10.0.1.249:8080/>", host: "<http://argo-cd.home.portefaix.xyz|argo-cd.home.portefaix.xyz>"
ingress-nginx-controller-lcxrb controller 2023/12/28 09:11:18 [alert] 24#24: worker process 5648 exited on signal 4 (core dumped)
ingress-nginx-controller-b88sj controller 2023/12/28 09:11:18 [error] 201#201: *885331 recv() failed (104: Connection reset by peer) while reading response header from upstream, client: 10.0.1.77, server: <http://argo-cd.home.portefaix.xyz|argo-cd.home.portefaix.xyz>, request: " GET  / HTTP/1.1", upstream: "<http://10.0.1.249:8080/>", host: "<http://argo-cd.home.portefaix.xyz|argo-cd.home.portefaix.xyz>"
the only ingress controller pod which respond a 
200
is 
ingress-nginx-controller-k794d
which is on the same host of the argo-cd server pod ... the k8s master
ok i downgrade Argo-CD chart from 5.51.6 to 5.46.7 and it works fine now ....
😞
Open in Slack
PreviousNext
Powered by