From d58b78d05898bd94a6278eb9f4ca2f438f65d71f Mon Sep 17 00:00:00 2001 From: Weihua Meng Date: Sat, 9 Sep 2017 11:18:05 -0500 Subject: [PATCH] Update opaque-integer-resource-node.md (#5330) typo correction --- docs/tasks/administer-cluster/opaque-integer-resource-node.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/tasks/administer-cluster/opaque-integer-resource-node.md b/docs/tasks/administer-cluster/opaque-integer-resource-node.md index 71925c1642..026488ebe2 100644 --- a/docs/tasks/administer-cluster/opaque-integer-resource-node.md +++ b/docs/tasks/administer-cluster/opaque-integer-resource-node.md @@ -134,7 +134,7 @@ opaque-int-resource-special-storage. ```yaml Capacity: ... - pod.alpha.kubernetes.io/opaque-int-special-storage: 8 + pod.alpha.kubernetes.io/opaque-int-resource-special-storage: 8 ``` If you want to allow arbitrary requests for special storage, you @@ -144,7 +144,7 @@ could advertise special storage in chunks of size 1 byte. In that case, you woul ```yaml Capacity: ... - pod.alpha.kubernetes.io/opaque-int-special-storage: 8Gi + pod.alpha.kubernetes.io/opaque-int-resource-special-storage: 8Gi ``` Then a Container could request any number of bytes of special storage, up to 800Gi.