Added DNS troubleshooting steps in EKS Anywhere troubleshooting doc #9085
Conversation
eks-distro-bot
added
the
size/M
jhaanvi5
changed the title
| DNS resolution is managed by coreDNS, a DNS server deployed as a pod within the cluster, it helps resolve service names to corresponding IP Addresses. If DNS resolution fails, applications maybe unable to connect to services or external endpoints. | ||
|
|
||
| #### Common errors related to DNS issues: | ||
| - Pods are unable to resolve the DNS names of other services. |
There was a problem hiding this comment.
this is one issue customer can face, you should also add the issue that we noticed- where a workload cluster could not be created as coredns was not connected to correct nameserver.
| kubectl logs --namespace=kube-system -l k8s-app=kube-dns | ||
| ``` | ||
| See if there are any suspicious or unexpected messages in the logs. | ||
| 3. Verify CoreDNS configuration and ensure it matches with cluster requirement, also verify if forward plugin points to correct DNS servers |
There was a problem hiding this comment.
Its not clear what we want customers to verify here, or how they ensure that coredns is actually connected to the right nameserver
There was a problem hiding this comment.
We want customer to verify the nameserver by inspecting CoreDNS configuration in Corefile, it would either be defined in CoreFile as forward . /etc/resolv.conf or directly as forward . 8.8.8.8, to inspect /etc/resolv.conf customer or on-call support can use below steps to create debug pod and inspect /etc/resolv.conf, do you mean we should refer to below steps here in this section, to inspect /etc/resolv.conf?
Verify CoreDNS configuration and ensure it matches with cluster requirement
In this point, what I meant is one should verify if the CoreDNS configMap has the correct nameserver which was set by admin/networking team.
eks-distro-bot
added
size/L
|
/approve |
|
@ndeksa: changing LGTM is restricted to collaborators In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: ndeksa The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Description of changes:
Added DNS troubleshooting tips in EKSA troubleshooting doc.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.