Merge pull request #6708 from vikaschoudhary16/er-resource-req

Fix Extended Resources consumption documentation

docs/concepts/configuration/manage-compute-resources-container.md

@@ -507,7 +507,7 @@ JSON-Pointer. For more details, see
 {: .note}
 
 To consume an Extended Resource in a Pod, include the resource name as a key
-in the `spec.containers[].resources.requests` map.
+in the `spec.containers[].resources.limits` map in the container spec.
 
 **Note:** Extended resources cannot be overcommitted, so request and limit
 must be equal if both are present in a container spec.
@@ -535,6 +535,8 @@ spec:
       requests:
         cpu: 2
         example.com/foo: 1
+      limits:
+        example.com/foo: 1
 ```
 
 ## Planned Improvements

docs/tasks/configure-pod-container/extended-resource-pod-2.yaml

@@ -9,3 +9,5 @@ spec:
     resources:
       requests:
         example.com/dongle: 2
+      limits:
+        example.com/dongle: 2

docs/tasks/configure-pod-container/extended-resource-pod.yaml

@@ -9,3 +9,5 @@ spec:
     resources:
       requests:
         example.com/dongle: 3
+      limits:
+        example.com/dongle: 3

docs/tasks/configure-pod-container/extended-resource.md

@@ -59,6 +59,8 @@ kubectl describe pod extended-resource-demo
 The output shows dongle requests:
 
 ```yaml
+Limits:
+  example.com/dongle: 3
 Requests:
   example.com/dongle: 3
 ```