From 4a25ad0805b405d74d1ef06dd9da01843b11837b Mon Sep 17 00:00:00 2001 From: okumin Date: Sun, 7 Jan 2018 21:06:03 +0900 Subject: [PATCH] Link to extended resources instead of deprecated opaque integer resources --- docs/concepts/configuration/taint-and-toleration.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/concepts/configuration/taint-and-toleration.md b/docs/concepts/configuration/taint-and-toleration.md index 463ab28b33..ebf153aa2d 100644 --- a/docs/concepts/configuration/taint-and-toleration.md +++ b/docs/concepts/configuration/taint-and-toleration.md @@ -171,7 +171,7 @@ the special nodes and hence the admission controller should add the toleration. To ensure that the pods that need the special hardware *only* schedule onto the nodes that have the special hardware, you will need some additional mechanism, e.g. you could represent the special resource using -[opaque integer resources](/docs/concepts/configuration/manage-compute-resources-container/#opaque-integer-resources-alpha-feature) +[extended resources](/docs/concepts/configuration/manage-compute-resources-container/#extended-resources) and request it as a resource in the PodSpec, or you could label the nodes that have the special hardware and use node affinity on the pods that need the hardware.