kubernetes
/
website
mirror of https://github.com/kubernetes/website.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #29883 from lxlxok/main 

Fix the page links to a section that doesn't exist
This commit is contained in:
Kubernetes Prow Robot 2021-10-06 05:58:33 -07:00 committed by GitHub
parent 37aa6b13e2 abadaf1ead
commit 35abb6e9f2
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
content/en/docs/concepts/services-networking/dns-pod-service.md
View File

@ -217,13 +217,13 @@ following pod-specific DNS policies. These policies are specified in the
- "`Default`": The Pod inherits the name resolution configuration from the node - "`Default`": The Pod inherits the name resolution configuration from the node
that the pods run on. that the pods run on.
See [related discussion](/docs/tasks/administer-cluster/dns-custom-nameservers/#inheriting-dns-from-the-node) See [related discussion](/docs/tasks/administer-cluster/dns-custom-nameservers)
for more details. for more details.
- "`ClusterFirst`": Any DNS query that does not match the configured cluster - "`ClusterFirst`": Any DNS query that does not match the configured cluster
domain suffix, such as "`www.kubernetes.io`", is forwarded to the upstream domain suffix, such as "`www.kubernetes.io`", is forwarded to the upstream
nameserver inherited from the node. Cluster administrators may have extra nameserver inherited from the node. Cluster administrators may have extra
stub-domain and upstream DNS servers configured. stub-domain and upstream DNS servers configured.
See [related discussion](/docs/tasks/administer-cluster/dns-custom-nameservers/#effects-on-pods) See [related discussion](/docs/tasks/administer-cluster/dns-custom-nameservers)
for details on how DNS queries are handled in those cases. for details on how DNS queries are handled in those cases.
- "`ClusterFirstWithHostNet`": For Pods running with hostNetwork, you should - "`ClusterFirstWithHostNet`": For Pods running with hostNetwork, you should
explicitly set its DNS policy "`ClusterFirstWithHostNet`". explicitly set its DNS policy "`ClusterFirstWithHostNet`".

2
content/en/docs/tasks/administer-cluster/dns-debugging-resolution.md
View File

@ -67,7 +67,7 @@ If the `nslookup` command fails, check the following:
### Check the local DNS configuration first ### Check the local DNS configuration first
Take a look inside the resolv.conf file. Take a look inside the resolv.conf file.
(See [Inheriting DNS from the node](/docs/tasks/administer-cluster/dns-custom-nameservers/#inheriting-dns-from-the-node) and (See [Customizing DNS Service](/docs/tasks/administer-cluster/dns-custom-nameservers) and
[Known issues](#known-issues) below for more information) [Known issues](#known-issues) below for more information)
```shell ```shell