From b3664e80dfaca4e46bb19570f8f0276d66ccc97f Mon Sep 17 00:00:00 2001 From: lemon-tree Date: Fri, 18 Aug 2017 04:51:45 +0800 Subject: [PATCH] Update labels-annotations-taints.md (#4987) Added the lost ".", and modified the "." in the brackets . --- docs/reference/labels-annotations-taints.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/reference/labels-annotations-taints.md b/docs/reference/labels-annotations-taints.md index e159fbf818..6ca88a83d2 100644 --- a/docs/reference/labels-annotations-taints.md +++ b/docs/reference/labels-annotations-taints.md @@ -63,7 +63,7 @@ of requiring a `g2.2xlarge`) ## failure-domain.beta.kubernetes.io/region -See [failure-domain.beta.kubernetes.io/zone](#failure-domainbetakubernetesiozone) +See [failure-domain.beta.kubernetes.io/zone](#failure-domainbetakubernetesiozone). ## failure-domain.beta.kubernetes.io/zone @@ -82,8 +82,8 @@ On the PersistentVolume: The `PersistentVolumeLabel` admission controller will a on GCE and AWS. Kubernetes will automatically spread the pods in a replication controller or service across nodes in a single-zone -cluster (to reduce the impact of failures.) With multiple-zone clusters, this spreading behaviour is extended -across zones (to reduce the impact of zone failures.) This is achieved via SelectorSpreadPriority. +cluster (to reduce the impact of failures). With multiple-zone clusters, this spreading behaviour is extended +across zones (to reduce the impact of zone failures). This is achieved via SelectorSpreadPriority. This is a best-effort placement, and so if the zones in your cluster are heterogeneous (e.g. different numbers of nodes, different types of nodes, or different pod resource requirements), this might prevent equal spreading of