Lab 11.3 -step 12 - IP where from ?

aristideboisseau

Hi there,

I'm wondering where the IP below is coming from:
student@cp:˜$ curl --resolve shop.example.com:32500:10.2.0.30 http://shop.example.com:32500/

but above we have this:
student@cp:˜$ kubectl get service/nginx-gateway -n nginx-gateway
service/nginx-gateway patched
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
nginx-gateway NodePort 10.111.70.106 80:32500/TCP,443:32730/TCP 11m

Am I not understanding the lab?

BR

chrispokorni

Hi @aristideboisseau,

The latest release of the lab guide has clear instructions for step 12:

sending a request to the Node IP and node port of the NGINX gateway

The NodePort is set to 32500 by patching the nginx-gateway service earlier in step 5, and the IP is your node's IP (private or public, depending on your infrastructure).

Regards,
-Chris

aristideboisseau

Hi Chris,

I'm running multipass for my infra, I tried many IPs but I'm having this error after successfully following all the lab steps :
curl --resolve shop.example.com:30645:10.0.1.68 http://shop.example.com:/30645
curl: (6) Could not resolve host: shop.example.com

---- Infos ----
multipass list
Name State IPv4 Image
cp1 Running 192.168.64.24 Ubuntu 24.04 LTS
10.0.0.184
worker1 Running 192.168.64.25 Ubuntu 24.04 LTS
10.0.1.68

ubuntu@cp1:~$ kubectl get nodes -o wide
NAME STATUS ROLES AGE VERSION INTERNAL-IP EXTERNAL-IP OS-IMAGE KERNEL-VERSION CONTAINER-RUNTIME
cp Ready control-plane 85d v1.32.4 192.168.64.24 Ubuntu 24.04.2 LTS 6.8.0-63-generic containerd://1.7.27
worker1 Ready 85d v1.32.4 192.168.64.25 Ubuntu 24.04.2 LTS 6.8.0-63-generic containerd://1.7.27

ubuntu@cp1:~$ kubectl get svc -n nginx-gateway
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
nginx-gateway NodePort 10.111.238.9 80:30645/TCP,443:30574/TCP 34m

ubuntu@cp1:~$ kubectl get pod -n nginx-gateway -o wide
NAME READY STATUS RESTARTS AGE IP NODE NOMINATED NODE READINESS GATES
nginx-gateway-96f76cdcf-bffz2 2/2 Running 0 42m 10.0.1.207 worker1

BR,
Aristide

chrispokorni

Hi @aristideboisseau,

If you followed the configuration steps from the lab guide, the curl command should be successful to the multipass IP address of either of the two nodes/VMs.

Regards,
-Chris