Can't get pods/nodes on worker but can on cp even though kubelet logs on both are failing

Hi@chrispokorni, Thanks for your prompt response but the problem is curl to a pod scheduled on the worker node
fails but works fine on cp node. Here is the output
`student@cp:~$ k apply -f LFD259/SOLUTIONS/s_02/basic.yaml
pod/basicpod created
student@cp:~$ k get po -o wide
NAME READY STATUS RESTARTS AGE IP NODE NOMINATED NODE READINESS GATES
basicpod 1/1 Running 0 10s 10.0.1.173 worker
student@cp:~$ curl 10.0.1.173 -v

• Trying 10.0.1.173:80...
• TCP_NODELAY set
  ^C
  student@cp:~$ k get no -o wide
  NAME STATUS ROLES AGE VERSION INTERNAL-IP EXTERNAL-IP OS-IMAGE KERNEL-VERSION CONTAINER-RUNTIME
  cp Ready control-plane 5h48m v1.28.1 159.89.28.137 Ubuntu 20.04.6 LTS 5.4.0-122-generic containerd://1.6.25
  worker Ready 40m v1.28.1 165.232.67.160 Ubuntu 20.04.6 LTS 5.4.0-122-generic containerd://1.6.25
  student@cp:~$ k get no
  NAME STATUS ROLES AGE VERSION
  cp Ready control-plane 5h49m v1.28.1
  worker Ready 41m v1.28.1`

Hi @support team, is there any hope to get response?