Score:0

Why did my AWS ELB failed? No route to host

in flag

I have tried to install Jenkins on Kubernetes cluster,but can not connect to my ELB

k get svc
NAME            TYPE        CLUSTER-IP       EXTERNAL-IP   PORT(S)     AGE
jenkins         ClusterIP   10.100.197.198   <none>        80/TCP      41m
jenkins-agent   ClusterIP   10.100.6.195     <none>        50000/TCP   41m
kubernetes      ClusterIP   10.100.0.1       <none>        443/TCP     62m

When I describe my jenkins service

Name:                  jenkins
Namespace:             default
Labels:                app.kubernetes.io/component=jenkins-controller
                       app.kubernetes.io/instance=jenkins
                       app.kubernetes.io/managed-by=Helm
                       app.kubernetes.io/name=jenkins
                       helm.sh/chart=jenkins-4.3.5
Annotations:           meta.helm.sh/release-name: jenkins
                       meta.helm.sh/release-namespace: default
                       service.beta.kubernetes.io/aws-load-balancer-type: nlb-ip
Selector:              app.kubernetes.io/component=jenkins-controller,app.kubernetes.io/instance=jenkins
Type:                  ClusterIP
IP Family Policy:      SingleStack
IP Families:           IPv4
IP:                    10.100.197.198
IPs:                   10.100.197.198
LoadBalancer Ingress:  k8s-default-jenkins-7bf4320d12-c7076e288dce55ca.elb.us-east-1.amazonaws.com
Port:                  http  80/TCP
TargetPort:            8080/TCP
Endpoints:             <none>
Session Affinity:      None
Events:
  Type    Reason                  Age   From     Message
  ----    ------                  ----  ----     -------
  Normal  SuccessfullyReconciled  47m   service  Successfully reconciled

It does not work

curl -v k8s-default-jenkins-7bf4320d12-c7076e288dce55ca.elb.us-east-1.amazonaws.com
*   Trying 192.168.79.13:80...
* TCP_NODELAY set
* connect to 192.168.79.13 port 80 failed: No route to host
*   Trying 192.168.126.109:80...
* TCP_NODELAY set
* connect to 192.168.126.109 port 80 failed: No route to host
* Failed to connect to k8s-default-jenkins-7bf4320d12-c7076e288dce55ca.elb.us-east-1.amazonaws.com port 80: No route to host
* Closing connection 0
curl: (7) Failed to connect to k8s-default-jenkins-7bf4320d12-c7076e288dce55ca.elb.us-east-1.amazonaws.com port 80: No route to host

From chrome I got error This site can’t be reached

ERR_ADDRESS_UNREACHABLE

Why?

I sit in a Tesla and translated this thread with Ai:

mangohost

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.