From 79090cc7cd9aaf4365e55e19b3ed7e4634ff883c Mon Sep 17 00:00:00 2001 From: Guangya Liu Date: Wed, 12 Apr 2017 18:23:16 +0800 Subject: [PATCH] `failure-domain` is no longer used in command line arg. --- docs/concepts/configuration/assign-pod-node.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/concepts/configuration/assign-pod-node.md b/docs/concepts/configuration/assign-pod-node.md index 19d4a3a0c7..1566e3b8f0 100644 --- a/docs/concepts/configuration/assign-pod-node.md +++ b/docs/concepts/configuration/assign-pod-node.md @@ -183,8 +183,8 @@ flavor and the `preferredDuringSchedulingIgnoredDuringExecution` flavor. As with node affinity, the legal operators for pod affinity and anti-affinity are `In`, `NotIn`, `Exists`, `DoesNotExist`, `Gt`, `Lt`. In principle, the `topologyKey` can be any legal label value. However, -for performance reasons, only a limit set of topology keys are allowed; -they are specified in the `--failure-domain` command-line argument to the scheduler. By default the allowed topology keys are +for performance reasons, only a limited set of topology keys are allowed. +By default the allowed topology keys are: * `kubernetes.io/hostname` * `failure-domain.beta.kubernetes.io/zone`