Issues in lab 3.2: hostIp set without hostPort; curl fails to connect when verifying repo

Here's the output of kubectl describe po nginx-6b47bcc6c6-97rfh:

Name:             nginx-6b47bcc6c6-97rfh
Namespace:        default
Priority:         0
Service Account:  default
Node:             ip-172-31-17-33/172.31.17.33
Start Time:       Wed, 22 Nov 2023 15:50:01 +0000
Labels:           io.kompose.service=nginx
                  pod-template-hash=6b47bcc6c6
Annotations:      <none>
Status:           Running
IP:               10.0.1.253
IPs:
  IP:           10.0.1.253
Controlled By:  ReplicaSet/nginx-6b47bcc6c6
Containers:
  nginx:
    Container ID:   containerd://a5fb3bb989266311c4b71b172c2e637e9a2c1e729bed976a88d9a85d1718125b
    Image:          nginx:1.12
    Image ID:       docker.io/library/nginx@sha256:72daaf46f11cc753c4eab981cbf869919bd1fee3d2170a2adeac12400f494728
    Port:           443/TCP
    Host Port:      0/TCP
    State:          Running
      Started:      Tue, 28 Nov 2023 19:04:37 +0000
    Last State:     Terminated
      Reason:       Unknown
      Exit Code:    255
      Started:      Tue, 28 Nov 2023 18:55:17 +0000
      Finished:     Tue, 28 Nov 2023 19:04:23 +0000
    Ready:          True
    Restart Count:  4
    Environment:    <none>
    Mounts:
      /etc/nginx/conf.d from nginx-claim0 (rw)
      /var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-mtwbk (ro)
Conditions:
  Type              Status
  Initialized       True 
  Ready             True 
  ContainersReady   True 
  PodScheduled      True 
Volumes:
  nginx-claim0:
    Type:       PersistentVolumeClaim (a reference to a PersistentVolumeClaim in the same namespace)
    ClaimName:  nginx-claim0
    ReadOnly:   false
  kube-api-access-mtwbk:
    Type:                    Projected (a volume that contains injected data from multiple sources)
    TokenExpirationSeconds:  3607
    ConfigMapName:           kube-root-ca.crt
    ConfigMapOptional:       <nil>
    DownwardAPI:             true
QoS Class:                   BestEffort
Node-Selectors:              <none>
Tolerations:                 node.kubernetes.io/not-ready:NoExecute op=Exists for 300s
                             node.kubernetes.io/unreachable:NoExecute op=Exists for 300s
Events:
  Type     Reason            Age                  From               Message
  ----     ------            ----                 ----               -------
  Warning  FailedScheduling  6d3h                 default-scheduler  0/2 nodes are available: pod has unbound immediate PersistentVolumeClaims. preemption: 0/2 nodes are available: 2 Preemption is not helpful for scheduling..
  Warning  FailedScheduling  6d3h (x2 over 6d3h)  default-scheduler  0/2 nodes are available: pod has unbound immediate PersistentVolumeClaims. preemption: 0/2 nodes are available: 2 Preemption is not helpful for scheduling..
  Normal   Scheduled         6d3h                 default-scheduler  Successfully assigned default/nginx-6b47bcc6c6-97rfh to ip-172-31-17-33
  Normal   Pulled            6d3h                 kubelet            Container image "nginx:1.12" already present on machine
  Normal   Created           6d3h                 kubelet            Created container nginx
  Normal   Started           6d3h                 kubelet            Started container nginx
  Normal   SandboxChanged    6d                   kubelet            Pod sandbox changed, it will be killed and re-created.
  Normal   Pulled            6d                   kubelet            Container image "nginx:1.12" already present on machine
  Normal   Created           6d                   kubelet            Created container nginx
  Normal   Started           6d                   kubelet            Started container nginx
  Normal   SandboxChanged    5h8m                 kubelet            Pod sandbox changed, it will be killed and re-created.
  Normal   Pulled            5h8m                 kubelet            Container image "nginx:1.12" already present on machine
  Normal   Created           5h8m                 kubelet            Created container nginx
  Normal   Started           5h8m                 kubelet            Started container nginx
  Normal   SandboxChanged    11m                  kubelet            Pod sandbox changed, it will be killed and re-created.
  Normal   Pulled            10m                  kubelet            Container image "nginx:1.12" already present on machine
  Normal   Created           10m                  kubelet            Created container nginx
  Normal   Started           10m                  kubelet            Started container nginx
  Warning  NodeNotReady      5m30s                node-controller    Node is not ready
  Normal   SandboxChanged    109s                 kubelet            Pod sandbox changed, it will be killed and re-created.
  Normal   Pulled            97s                  kubelet            Container image "nginx:1.12" already present on machine
  Normal   Created           97s                  kubelet            Created container nginx
  Normal   Started           97s                  kubelet            Started container nginx

Here's the output offind $HOME -name local-repo-setup.sh:

/home/ubuntu/local-repo-setup.sh
/home/ubuntu/LFD259/SOLUTIONS/s_03/local-repo-setup.sh

Here's the output of sudo cat /etc/containers/registries.conf.d/registry.conf and grep endpoint /etc/containerd/config.toml, on the CP respectively:

[[registry]]
location = "10.97.40.62:5000"
insecure = true

    endpoint = ""
endpoint = ["http://10.97.40.62:5000"]

Here's the output of sudo cat /etc/containers/registries.conf.d/registry.conf and grep endpoint /etc/containerd/config.toml, on the WORKER respectively:

cat: /etc/containers/registries.conf.d/registry.conf: No such file or directory

    endpoint = ""

The following commands are not listing multiple nginx and registry pods:

kubectl get po nginx -o wide
kubectl get po registry -o wide

On the CP:

Error from server (NotFound): pods "nginx" not found
Error from server (NotFound): pods "registry" not found

On the worker:

E1128 19:13:22.296309    1998 memcache.go:265] couldn't get current server API group list: Get "http://localhost:8080/api?timeout=32s": dial tcp 127.0.0.1:8080: connect: connection refused
E1128 19:13:22.296882    1998 memcache.go:265] couldn't get current server API group list: Get "http://localhost:8080/api?timeout=32s": dial tcp 127.0.0.1:8080: connect: connection refused
E1128 19:13:22.298355    1998 memcache.go:265] couldn't get current server API group list: Get "http://localhost:8080/api?timeout=32s": dial tcp 127.0.0.1:8080: connect: connection refused
E1128 19:13:22.299715    1998 memcache.go:265] couldn't get current server API group list: Get "http://localhost:8080/api?timeout=32s": dial tcp 127.0.0.1:8080: connect: connection refused
E1128 19:13:22.301115    1998 memcache.go:265] couldn't get current server API group list: Get "http://localhost:8080/api?timeout=32s": dial tcp 127.0.0.1:8080: connect: connection refused
The connection to the server localhost:8080 was refused - did you specify the right host or port?

The endpoints on the control plane:
```
nginx 10.0.1.253:443 6d3h
registry 10.0.1.210:5000 6d3h
...

And on the worker the connection is refused.

Thanks for your help!

Hey @chrispokorni !
There are no instructions for configuring the worker node in lab 3, exercises 1 and 2. The last command issued on the worker was in 2.2.