https://jira.akraino.org This file is an XML representation of an issue en-us 9.4.5 940005 11-04-2023 https://jira.akraino.org/browse/REC-36 Radio Edge Cloud <ol> <li>DNS should provide DNS for External Name Services</li> <li>DNS should provide DNS for PODs for internal host names and sub-domains</li> <li>DNS should provide DNS for Services</li> <li>DNS should provide DNS for cluster</li> </ol> REC-36

DNS Server check

Sub-task REC-31 Medium In Progress Unresolved Naga Sugguna Deepak Kataria Mon, 26 Aug 2019 18:18:21 +0000 Tue, 22 Oct 2019 15:51:45 +0000 0 2 <p><a href="https://gerrit.akraino.org/r/c/ta/cloudtaf/+/1809/2/testcases/basic_func_tests/tc_005_ssh_dns_server_check.py" class="external-link" target="_blank" rel="nofollow noopener">https://gerrit.akraino.org/r/c/ta/cloudtaf/+/1809/2/testcases/basic_func_tests/tc_005_ssh_dns_server_check.py</a></p> <p>Naga committed code to-day (10/15/19), it is under review</p> <p>Naga removed the dependency on external static yaml files and images. He created a common ROBOT library to create busy box and NGNIX PODs. He is yet to commit code, since aknode82 is down,</p> <p>Naga is working on this and will commit code today</p> <p>Naga did not have a time to work on this to-day.</p> <p>Krisztian gave -1, Naga is looking into this.</p> <p>Naga is waiting for review on gerrit commit 1489.</p> <p>This item is pending review.</p> <p>This is still under review</p> <p>KINKWAN will review this</p> <p>Naga is waiting for review.</p> <p>This was completed, code committed and is under review</p> <p>Ingress is completely different from DNS. So will test ingress in different story but here we verify only DNS. Here are the manual steps to do DNS verification<br/> This is prepared based on k8s documentation available at <a href="https://kubernetes.io/docs/tasks/administer-cluster/dns-debugging-resolution/" class="external-link" target="_blank" rel="nofollow noopener">https://kubernetes.io/docs/tasks/administer-cluster/dns-debugging-resolution/</a></p> <p>kubectl create deployment nginx --image=nginx<br/> kubectl expose deployment nginx --port=80<br/> curl nginx.default.svc.rec.io<br/> it should have &lt;h1&gt;Welcome to nginx!&lt;/h1&gt;</p> <p>Traefik Ingress Controller is manually verified and found its working fine.<br/> Hare are the steps followed</p> <p>wget <a href="https://raw.githubusercontent.com/containous/traefik/v1.7/examples/k8s/traefik-rbac.yaml" class="external-link" target="_blank" rel="nofollow noopener">https://raw.githubusercontent.com/containous/traefik/v1.7/examples/k8s/traefik-rbac.yaml</a><br/> kubectl create -f traefik-rbac.yaml<br/> wget <a href="https://raw.githubusercontent.com/containous/traefik/v1.7/examples/k8s/traefik-ds.yaml" class="external-link" target="_blank" rel="nofollow noopener">https://raw.githubusercontent.com/containous/traefik/v1.7/examples/k8s/traefik-ds.yaml</a><br/> kubectl create -f traefik-ds.yaml<br/> kubectl create -f <a href="https://gist.githubusercontent.com/geraldcroes/19873ea100eeea907624cb3e157e17b5/raw/78adfaca8d6a84304f560cb147ee9a6cb6df9c14/whoami-deployment.yml" class="external-link" target="_blank" rel="nofollow noopener">https://gist.githubusercontent.com/geraldcroes/19873ea100eeea907624cb3e157e17b5/raw/78adfaca8d6a84304f560cb147ee9a6cb6df9c14/whoami-deployment.yml</a><br/> kubectl create -f <a href="https://gist.githubusercontent.com/geraldcroes/36de6ce6a027ac574bff8ef169f34fed/raw/085d63bef1e763e4d6e4b94251aa1762bf9c8061/whoami-service.yml" class="external-link" target="_blank" rel="nofollow noopener">https://gist.githubusercontent.com/geraldcroes/36de6ce6a027ac574bff8ef169f34fed/raw/085d63bef1e763e4d6e4b94251aa1762bf9c8061/whoami-service.yml</a><br/> kubectl create -f <a href="https://gist.githubusercontent.com/geraldcroes/5758d32f2074bee94940fe4a4d2f2880/raw/31d184c0870055fbc7be17228a96c9bfa10ba638/whoami-ingress.yml" class="external-link" target="_blank" rel="nofollow noopener">https://gist.githubusercontent.com/geraldcroes/5758d32f2074bee94940fe4a4d2f2880/raw/31d184c0870055fbc7be17228a96c9bfa10ba638/whoami-ingress.yml</a><br/> curl -H "Host: whoami.localhost" 10.244.2.35:80<br/> kubectl create -f <a href="https://gist.githubusercontent.com/geraldcroes/98253cce7bed32ae864a35a40af3bd41/raw/660c724c16aff07cf00d8fda689c11302142f384/whoareyou.yml" class="external-link" target="_blank" rel="nofollow noopener">https://gist.githubusercontent.com/geraldcroes/98253cce7bed32ae864a35a40af3bd41/raw/660c724c16aff07cf00d8fda689c11302142f384/whoareyou.yml</a><br/> curl -H "Host: whoareyou.localhost" 10.254.224.181</p> <p>Naga will try with Traefik Ingress Controller today.</p> <p>Naga is still  exploring installing NGINX Ingress Controller, which is not working. Naga is trying with Traefik Ingress Controller.</p> <p>To test ingress ingress controller should be already there on cluster but its not there. I tried to add ingress controller by following <a href="https://kubernetes.github.io/ingress-nginx/deploy/#verify-installation" class="external-link" target="_blank" rel="nofollow noopener">NGINX Ingress Controller </a> but its failing while verification. Due to there is no ingress controller running, and con't test ingress as of now. Looking into this issue further.</p> <p>Naga is trying to figure out manual tests to execute</p> <p>No update on this.</p> <p>Naga did not have a chance to work on this.</p> <p>Naga did not get a chance to work on this.</p> <p>Naga did not get a chance to work on this yet.</p> <p>Naga will work to address the review comments and update tests accordingly</p> <p>as commented on Gerrit: IMO the test shouldn't blindly assume the presence of optional features, such as 1: availability of external connectivity from the test Pod without explicitly setting it up 2: availability of upstream DNS server</p> <p>in fact, configuring and validating upstream DNS server should be an explicitly tested step. i.e. upstream DNS resolve should not work when an upstream DNS server is not configured, and vica-versa</p> <p>Naga is addressing -1 review comments from Paul Carver and Levente Kale.</p> <p>Naga has tested this manually and will work on ROBOT test integration next. Targeting to complete ROBOT integration and committing code to Gerrit by to-morrow.</p> <p>DNS Server manually checked on OE2 cluster. OE1 cluster is not working due to cluster issues. Here are the step followed to verify DNS Server is working as expected </p> <p>$ kubectl apply -f <a href="https://k8s.io/examples/application/deployment.yaml" class="external-link" target="_blank" rel="nofollow noopener">https://k8s.io/examples/application/deployment.yaml</a><br/> $ kubectl expose deployment nginx-deployment<br/> $ kubectl get svc<br/> $ curl 10.254.2.52<br/> $ kubectl exec -it nginx-deployment-5754944d6c-zsnb6 &#8211; cat /etc/resolv.conf</p> <ol> <li> <ol> <li>output ##<br/> nameserver 10.254.0.254<br/> search default.svc.rec.io svc.rec.io rec.io<br/> options ndots:5</li> </ol> </li> </ol> <p>$ kubectl exec -it nginx-deployment-5754944d6c-zsnb6 &#8211; ping google.com</p> <p>Naga has completed manual testing on aknode30 (REC). Latest image is on OE1/OE2, Naga will do manual testing on this cluster, Working on ROBOT automation. Will test and commit code by to-morrow (8/28). Manually created service and will access it from kube-dns.</p> Development Rank 0|i001fj: