Mirrors/coredns
1
0
Fork 0
mirror of https://github.com/coredns/coredns.git synced 2025-11-01 02:33:14 -04:00
Code Issues Packages Projects Releases Wiki Activity

Fix several typos in docs. (#426)

Browse Source 
Fixes several typos in docs.

Signed-off-by: Yong Tang <yong.tang.github@outlook.com>
This commit is contained in:
Yong Tang
2016-11-13 23:25:17 -08:00
committed by Miek Gieben
parent 43b2519eca
commit 137fc33b8f
3 changed files with 3 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
middleware/kubernetes/README.md
View File

@@ -16,7 +16,7 @@ The record name format can be changed by specifying a name template in the Coref
kubernetes [ZONES...]
~~~
* `ZONES` zones kubernetes should be authorative for. Overlapping zones are ignored.
* `ZONES` zones kubernetes should be authoritative for. Overlapping zones are ignored.
Or if you want to specify an endpoint:

2
middleware/kubernetes/SkyDNS.md
View File

@@ -27,7 +27,7 @@ an entry: `1-2-3-4.default.pod.cluster.local.`
####A Records and hostname Based on Pod Annotations - A Beta Feature in Kubernetes v1.2
Currently when a pod is created, its hostname is the Pod's `metadata.name` value.
With v1.2, users can specify a Pod annotation, `pod.beta.kubernetes.io/hostname`, to specify what the Pod's hostname should be.
If the annotation is specified, the annotation value takes precendence over the Pod's name, to be the hostname of the pod.
If the annotation is specified, the annotation value takes precedence over the Pod's name, to be the hostname of the pod.
For example, given a Pod with annotation `pod.beta.kubernetes.io/hostname: my-pod-name`, the Pod will have its hostname set to "my-pod-name".
v1.2 introduces a beta feature where the user can specify a Pod annotation, `pod.beta.kubernetes.io/subdomain`, to specify what the Pod's subdomain should be.