https://rancher.com/ logo
#general
Title
# general
a

adamant-kite-43734

09/19/2022, 4:30 PM
This message was deleted.
1
p

proud-salesmen-12221

09/19/2022, 4:35 PM
Copy code
david@ubuntu:~/dev/rke2$ kubectl get all -o wide
NAME            READY   STATUS    RESTARTS   AGE     IP           NODE                    NOMINATED NODE   READINESS GATES
pod/busybox     1/1     Running   0          36m     10.42.1.23   rke2-agent1.rke2.test   <none>           <none>
pod/nginx-pod   1/1     Running   0          7m48s   10.42.2.47   rke2-agent2.rke2.test   <none>           <none>

NAME                        TYPE           CLUSTER-IP     EXTERNAL-IP     PORT(S)        AGE     SELECTOR
service/kubernetes          ClusterIP      10.43.0.1      <none>          443/TCP        2d15h   <none>
service/nginx-pod-service   LoadBalancer   10.43.153.37   192.168.1.240   80:32003/TCP   7m48s   <http://app.kubernetes.io/name=nginx-example|app.kubernetes.io/name=nginx-example>

david@ubuntu:~/dev/rke2$ kubectl get pod -n metallb-system -o wide
NAME                         READY   STATUS    RESTARTS      AGE   IP            NODE                     NOMINATED NODE   READINESS GATES
controller-6d5cb87f6-c5f5g   1/1     Running   1 (51m ago)   23h   10.42.2.144   rke2-agent2.rke2.test    <none>           <none>
speaker-cmh6c                1/1     Running   1 (51m ago)   23h   10.11.0.112   rke2-agent2.rke2.test    <none>           <none>
speaker-gljrr                1/1     Running   1 (51m ago)   23h   10.11.0.111   rke2-agent1.rke2.test    <none>           <none>
speaker-lq42s                1/1     Running   2 (51m ago)   23h   10.11.0.11    rke2-server1.rke2.test   <none>           <none>
I followed these MetalLB troubleshooting steps for checking ARPs and tcpdump and it looks good. https://metallb.universe.tf/configuration/troubleshooting/
I don't know if this reveals anything. From my busybox image, I'm able to wget the External-IP on port 80, but not port 32003.
Copy code
# server1 VM

[vagrant@rke2-server1 ~]$ kubectl get svc
NAME                TYPE           CLUSTER-IP     EXTERNAL-IP     PORT(S)        AGE
kubernetes          ClusterIP      10.43.0.1      <none>          443/TCP        2d17h
nginx-pod-service   LoadBalancer   10.43.153.37   192.168.1.240   80:32003/TCP   3h5m
Copy code
# busybox image

/ # wget -O - 192.168.1.240:80
Connecting to 192.168.1.240:80 (192.168.1.240:80)
writing to stdout
... omitted ...
<title>Welcome to nginx!</title>
... omitted ...
-                    100% |****************************************************************************************************************************|   615  0:00:00 ETA
written to stdout
Copy code
# busybox image

/ # wget -O - 192.168.1.240:32003
Connecting to 192.168.1.240:32003 (192.168.1.240:32003)
wget: can't connect to remote host (192.168.1.240): Connection timed out
Solved. My coworker was able to point out what I was missing- a route on my host machine to the external ip
161 Views