The Memory Manager graduates to Beta (#28851)

* Update gRPC messages documentation

* Revisions + extend docs

* Update content/en/docs/tasks/administer-cluster/memory-manager.md

Co-authored-by: Tim Bannister <tim@scalefactory.com>

* Revisions

* Update content/en/docs/tasks/administer-cluster/memory-manager.md

Co-authored-by: Qiming Teng <tengqm@outlook.com>

* Revisions

Co-authored-by: Tim Bannister <tim@scalefactory.com>
Co-authored-by: Qiming Teng <tengqm@outlook.com>

content/en/docs/concepts/extend-kubernetes/compute-storage-net/device-plugins.md

@@ -199,7 +199,7 @@ service PodResourcesLister {
 
 The `List` endpoint provides information on resources of running pods, with details such as the
 id of exclusively allocated CPUs, device id as it was reported by device plugins and id of
-the NUMA node where these devices are allocated.
+the NUMA node where these devices are allocated. Also, for NUMA-based machines, it contains the information about memory and hugepages reserved for a container.
 
 ```gRPC
 // ListPodResourcesResponse is the response returned by List function
@@ -219,6 +219,14 @@ message ContainerResources {
     string name = 1;
     repeated ContainerDevices devices = 2;
     repeated int64 cpu_ids = 3;
+    repeated ContainerMemory memory = 4;
+}
+
+// ContainerMemory contains information about memory and hugepages assigned to a container
+message ContainerMemory {
+    string memory_type = 1;
+    uint64 size = 2;
+    TopologyInfo topology = 3;
 }
 
 // Topology describes hardware topology of the resource
@@ -247,6 +255,7 @@ It provides more information than kubelet exports to APIServer.
 message AllocatableResourcesResponse {
     repeated ContainerDevices devices = 1;
     repeated int64 cpu_ids = 2;
+    repeated ContainerMemory memory = 3;
 }
 
 ```