From 45d12f48780590f5d31de0f514787c993fc18d2e Mon Sep 17 00:00:00 2001 From: Tamas Levai Date: Fri, 12 Jan 2024 09:45:16 +0100 Subject: [PATCH] 99-labs/02-webapps: Fix think-o in a cmd snippet --- 99-labs/02-webapps/README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/99-labs/02-webapps/README.md b/99-labs/02-webapps/README.md index 811eb54..44dc738 100644 --- a/99-labs/02-webapps/README.md +++ b/99-labs/02-webapps/README.md @@ -456,8 +456,8 @@ Hello world from helloworld-67f7d78ccd-2fklj! It seems one of our `helloworld` pods received the request and responded with its own pod name. Even better, we don't even need to remember `ClusterIPs`, as Kubernetes also exposes our services via DNS as well: ``` sh -kubectl exec -it net-debug -kubectl exec -it net-debug -- curl http://helloworld:8080 -Hello world from helloworld-67f7d78ccd-qn6wk! +kubectl exec -it net-debug -- curl http://helloworld:8080 +Hello world from helloworld-67f7d78ccd-qn6wk! ``` Kubernetes will resolve the domain name `helloworld` to the `ClusterIP` of the Service of the same name via `kube-dns` and use that IP to send the request. Use the `host` command to manually resolve the IP for the `helloworld` domain name: