Welcome to the Linux Foundation Forum!

lab 3.5 step 6

Hi I have issue with load page by browser, service nginx

kubectl get svc
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
httpd ClusterIP 10.97.249.136 8050/TCP 80m
kubernetes ClusterIP 10.96.0.1 443/TCP 5h25m
nginx LoadBalancer 10.109.23.170 80:32224/TCP 22m

the ip public not respond.
http://35.184.217.9:32224/

kubectl get pods
NAME READY STATUS RESTARTS AGE
httpd-88fb9b4f9-w47cx 1/1 Running 0 110m
nginx-85ff79dd56-9mdjg 1/1 Running 0 174m
nginx-85ff79dd56-jnrfr 1/1 Running 0 69m
nginx-85ff79dd56-p59bk 1/1 Running 0 64m

kubectl get pod -o wide
NAME READY STATUS RESTARTS AGE IP NODE NOMINATED NODE READINESS GATES
httpd-88fb9b4f9-w47cx 1/1 Running 0 110m 192.168.97.6 fat78
nginx-85ff79dd56-9mdjg 1/1 Running 0 174m 192.168.97.3 fat78
nginx-85ff79dd56-jnrfr 1/1 Running 0 69m 192.168.196.196 fat-1
nginx-85ff79dd56-p59bk 1/1 Running 0 64m 192.168.97.12 fat78

could you help me.

Comments

  • Hi @etofran810,

    Are you still on local vmware? Which one of your Kubernetes cluster instances has the public IP 35.184.217.9 ?

    Regards,
    -Chris

  • not, I am working with GCP

  • node1 us-central1-f 10.128.0.5 (nic0) 35.225.101.86
    node2 us-central1-f 10.128.0.6 (nic0) 35.202.241.245

  • I have created different service
    f_alexander_t_gmail_com@fat-1:~$ kubectl get svc
    NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
    httpd ClusterIP 10.97.249.136 8050/TCP 44h
    kubernetes ClusterIP 10.96.0.1 443/TCP 2d
    nginx LoadBalancer 10.109.23.170 80:32224/TCP 43h
    zabbix ClusterIP 10.106.199.184 50100/TCP 18m

    nginx type loadbalance
    the lab indicated connect for browser ip-public:port http://35.202.241.245:32224/

  • kubectl get pods --> 3 intance
    nginx-85ff79dd56-9mdjg 1/1 Running 1 45h
    nginx-85ff79dd56-jnrfr 1/1 Running 1 43h
    nginx-85ff79dd56-p59bk 1/1 Running 1 43h

  • ping -c 3 35.202.241.245
    PING 35.202.241.245 (35.202.241.245) 56(84) bytes of data.
    64 bytes from 35.202.241.245: icmp_seq=1 ttl=67 time=1.14 ms
    64 bytes from 35.202.241.245: icmp_seq=2 ttl=67 time=0.389 ms
    64 bytes from 35.202.241.245: icmp_seq=3 ttl=67 time=0.372 ms

    --- 35.202.241.245 ping statistics ---
    3 packets transmitted, 3 received, 0% packet loss, time 2009ms
    rtt min/avg/max/mdev = 0.372/0.634/1.143/0.360 ms

  • kubectl exec nginx-85ff79dd56-9mdjg -- printenv
    PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
    HOSTNAME=nginx-85ff79dd56-9mdjg
    HTTPD_SERVICE_HOST=10.97.249.136
    HTTPD_PORT_8050_TCP_PROTO=tcp
    KUBERNETES_PORT=tcp://10.96.0.1:443
    NGINX_SERVICE_HOST=10.109.23.170
    NGINX_PORT_80_TCP=tcp://10.109.23.170:80
    NGINX_PORT_80_TCP_PORT=80
    KUBERNETES_SERVICE_PORT_HTTPS=443
    KUBERNETES_PORT_443_TCP_PORT=443
    NGINX_SERVICE_PORT=80
    NGINX_PORT=tcp://10.109.23.170:80
    HTTPD_SERVICE_PORT=8050
    HTTPD_PORT=tcp://10.97.249.136:8050
    HTTPD_PORT_8050_TCP=tcp://10.97.249.136:8050
    HTTPD_PORT_8050_TCP_PORT=8050
    HTTPD_PORT_8050_TCP_ADDR=10.97.249.136
    KUBERNETES_SERVICE_PORT=443
    KUBERNETES_PORT_443_TCP_PROTO=tcp
    NGINX_PORT_80_TCP_PROTO=tcp
    NGINX_PORT_80_TCP_ADDR=10.109.23.170
    KUBERNETES_SERVICE_HOST=10.96.0.1
    KUBERNETES_PORT_443_TCP=tcp://10.96.0.1:443
    KUBERNETES_PORT_443_TCP_ADDR=10.96.0.1
    NGINX_VERSION=1.17.8
    NJS_VERSION=0.3.8
    PKG_RELEASE=1~buster
    HOME=/root

  • yes, I have opened all port

    Nombre Tipo Destinos Filtros Protocolos y puertos Acción Prioridad Red
    default-allow-icmp Entrada Aplicar a todas Intervalos de IPs: 0.0.0.0/0 icmp Permitir 65534default
    default-allow-internal Entrada Aplicar a todas Intervalos de IPs: 10.128.0.0/9 tcp:0-65535
    udp:0-65535
    icmp Permitir 65534 default
    default-allow-rdp Entrada Aplicar a todas Intervalos de IPs: 0.0.0.0/0 tcp:3389 Permitir 65534 default
    default-allow-ssh Entrada Aplicar a todas Intervalos de IPs: 0.0.0.0/0 tcp:22 Permitir 65534 default
    fat78 Entrada Aplicar a todas Intervalos de IPs: 192.168.116.0/24 all Permitir 1000 fat78

  • Hi @etofran810,

    My Spanish is a bit rusty, and I cannot see a rule that allows all traffic from all sources, to all ports and all protocols.
    Would you mind highlighting that particular rule?

    Regards,
    -Chris

Categories

Upcoming Training