@Tej_Singh_Rana @Mumshad Mannambeth @unnivkn @Hinodeya Hi, I'm doing some self p . . .

Kubernetes-Slack Discussions
#1

qoosuperman:
@Tej_Singh_Rana @Mumshad Mannambeth @unnivkn @Hinodeya
Hi, I’m doing some self practice base on this https://github.com/David-VTUK/CKA-StudyGuide/blob/master/LabGuide/03-Services%20%26%20Networking.md|link
And I’d like to find a way to prove the change on configmap below is effective after apply the change and delete dns pod
any recommend ways? :pray:

kubectl edit cm coredns -n kube-system 

replace:
forward . /etc/resolv.conf

with
forward . 8.8.8.8

# add this block
custom.local:53 {
        errors 
        cache 30
        forward . 10.5.4.223
        reload
    }
#2

Vinay:
tried --recording ?

#3

Phani M:
@qoosuperman you may try bringing up a test pod running busybox image and running a nslookup command to 1). any internal service - for testing the .cluster.local 2). http://www.google.com|www.google.com

Run a test pod and expose it by a service:

k run test1 --image=nginx --port 80 --expose 8080

Here is how you can spin a test Pod to run the above nslookup commands:

1. k run test-$RANDOM --image=busybox:1.28 -it --rm --restart=Never -- nslookup test1
2. k run test-$RANDOM --image=busybox:1.28 -it --rm --restart=Never -- nslookup <http://www.google.com|www.google.com>