From bc549fd3a0e5ed359d36cb9e573089669a52a231 Mon Sep 17 00:00:00 2001 From: Sharjeel Aziz Date: Mon, 23 Dec 2019 14:09:33 -0500 Subject: [PATCH] Minor fix for a typo. (#18182) --- content/en/docs/tasks/administer-cluster/topology-manager.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/docs/tasks/administer-cluster/topology-manager.md b/content/en/docs/tasks/administer-cluster/topology-manager.md index 1cb3d28f04..382038a3a5 100644 --- a/content/en/docs/tasks/administer-cluster/topology-manager.md +++ b/content/en/docs/tasks/administer-cluster/topology-manager.md @@ -99,7 +99,7 @@ If it is, Topology Manager will store this and the *Hint Providers* can then use resource allocation decision. If, however, this is not possible then the Topology Manager will reject the pod from the node. This will result in a pod in a `Terminated` state with a pod admission failure. -Once the pod is in a `Terminated` state, the Kubernetes scheduler will **not** attempt to reschedule the pod. It is recommended a Deployment with Replicas to trigger a redeploy of the pod. +Once the pod is in a `Terminated` state, the Kubernetes scheduler will **not** attempt to reschedule the pod. It is recommended to use a Deployment with replicas to trigger a redeploy of the Pod. An external control loop could be also implemented to trigger a redeployment of pods that have the `Topology Affinity` error. ### Pod Interactions with Topology Manager Policies