Welcome to the Linux Foundation Forum!

Lab 8.3 step 4 failed. Do I miss something?

zhangwezhangwe Posts: 45
in LFS258 Class Forum

I use kubectl -n accounting describe services
NodePort: 30731/TCP

[email protected]:~$ kubectl cluster-info
Kubernetes master is running at https://k8smaster:6443
KubeDNS is running at https://k8smaster:6443/api/v1/namespaces/kube-system/services/kube-dns:dns/proxy

curl http://k8smaster:30731
curl: (7) Failed to connect to k8smaster port 30731: Connection refused

Best Answer

Answers

  • serewiczserewicz Posts: 820

    Hello,

    I show Exercise 8.3, step 4 to be a delete command. I think you mean Exercise 8.2.

    Either the service is not running, or the pod is not running. What was the output of Ex 8.1, step 13 and Ex 8.2, step 1?

    If you run kubectl get pod -o wide --all-namespaces

    Does it show the nginx pod is running and in a 1/1 Ready status?

    Regards,

  • zhangwezhangwe Posts: 45

    Here is the information:

    Ex 8.1, step 13
    [email protected]:~$ kubectl -n accounting get pods -o wide
    NAME READY STATUS RESTARTS AGE IP NODE NOMINATED NODE READINESS GATES
    nginx-one-79c56b47b9-7tcxj 1/1 Running 0 8m 192.168.171.111 worker
    nginx-one-79c56b47b9-8z57b 1/1 Running 0 8m 192.168.171.112 worker

    Ex 8.2, step 1
    [email protected]:~$ kubectl -n accounting expose deployment \

    nginx-one --type=NodePort --name=service-lab

    service/service-lab exposed
    [email protected]:~$ kubectl get pod -o wide --all-namespaces
    NAMESPACE NAME READY STATUS RESTARTS AGE IP NODE NOMINATED NODE READINESS GATES
    accounting nginx-one-79c56b47b9-7tcxj 1/1 Running 0 14m 192.168.171.111 worker
    accounting nginx-one-79c56b47b9-8z57b 1/1 Running 0 14m 192.168.171.112 worker
    kube-system calico-kube-controllers-578894d4cd-crfg6 1/1 Running 5 4d17h 192.168.219.110 master
    kube-system calico-node-2kpx2 1/1 Running 5 4d17h 10.142.0.5 master
    kube-system calico-node-krnsk 1/1 Running 5 4d17h 10.142.0.6 worker
    kube-system coredns-66bff467f8-fxdxf 1/1 Running 4 3d11h 192.168.219.108 master
    kube-system coredns-66bff467f8-spj2s 1/1 Running 5 4d16h 192.168.219.109 master
    kube-system etcd-master 1/1 Running 5 4d17h 10.142.0.5 master
    kube-system kube-apiserver-master 1/1 Running 5 4d17h 10.142.0.5 master
    kube-system kube-controller-manager-master 1/1 Running 5 4d17h 10.142.0.5 master
    kube-system kube-proxy-7r5dx 1/1 Running 5 4d17h 10.142.0.6 worker
    kube-system kube-proxy-lms4p 1/1 Running 5 4d17h 10.142.0.5 master
    kube-system kube-scheduler-master 1/1 Running 5 4d17h 10.142.0.5 master
    low-usage-limit limited-hog-d9d756c45-76t8s 1/1 Running 3 2d21h 192.168.171.110 worker
    [email protected]:~$

    Ex 8.2, step 2
    [email protected]:~$ kubectl -n accounting describe services
    Name: service-lab
    Namespace: accounting
    Labels: system=secondary
    Annotations:
    Selector: system=secondary
    Type: NodePort
    IP: 10.97.208.233
    Port: 8088/TCP
    TargetPort: 8088/TCP
    NodePort: 30215/TCP
    Endpoints: 192.168.171.111:8088,192.168.171.112:8088
    Session Affinity: None
    External Traffic Policy: Cluster
    Events:

    Ex 8.2, step 3
    [email protected]:~$ kubectl cluster-info
    Kubernetes master is running at https://k8smaster:6443
    KubeDNS is running at https://k8smaster:6443/api/v1/namespaces/kube-system/services/kube-dns:dns/proxy

    Ex 8.2, step 4
    [email protected]:~$ curl http://k8smaster:30215
    curl: (7) Failed to connect to k8smaster port 30215: Connection refused

    After Connection refused
    [email protected]:~$ kubectl get pod -o wide -n accounting
    NAME READY STATUS RESTARTS AGE IP NODE NOMINATED NODE READINESS GATES
    nginx-one-79c56b47b9-7tcxj 1/1 Running 0 29m 192.168.171.111 worker
    nginx-one-79c56b47b9-8z57b 1/1 Running 0 29m 192.168.171.112 worker

  • zhangwezhangwe Posts: 45

    Thank you very much for your help.

  • serewiczserewicz Posts: 820

    My pleasure! :-)

Sign In or Register to comment.