Documentation update for pod level resources in 1.34

Author: ndixita

content/en/docs/concepts/configuration/manage-resources-containers.md

@@ -113,7 +113,7 @@ resource requests/limits of that type for each container in the Pod.
 
 {{< feature-state feature_gate_name="PodLevelResources" >}}
 
-Starting in Kubernetes 1.32, you can also specify resource requests and limits at
+Starting in Kubernetes 1.34, you can also specify resource requests and limits at
 the Pod level. At the Pod level, Kubernetes {{< skew currentVersion >}}
 only supports resource requests or limits for specific resource types: `cpu` and /
 or `memory`. This feature is currently in alpha and with the feature enabled,

content/en/docs/reference/command-line-tools-reference/feature-gates/PodLevelResources.md

@@ -9,6 +9,10 @@ stages:
   - stage: alpha
     defaultValue: false
     fromVersion: "1.32"
+    toVersion: "1.33"
+  - stage: beta
+    defaultValue: false
+    fromVersion: "1.34"
 ---
 Enable _Pod level resources_:  the ability to specify resource requests and limits
 at the Pod level, rather than only for specific containers.

content/en/docs/tasks/configure-pod-container/assign-pod-level-resources.md

@@ -2,7 +2,7 @@
 title: Assign Pod-level CPU and memory resources
 content_type: task
 weight: 30
-min-kubernetes-server-version: 1.32
+min-kubernetes-server-version: 1.34
 ---
 
 
@@ -43,6 +43,19 @@ The `PodLevelResources` [feature
 gate](/docs/reference/command-line-tools-reference/feature-gates/) must be enabled
 for your control plane and for all nodes in your cluster.
 
+## Limitations
+
+For Kubernetes {{< skew currentVersion >}}, resizing pod-level resources has the
+following limitations:
+
+* **Resource Types:** Only CPU, memory and hugepages resources can be specified at pod-level.
+* **Operating System:** Pod-level resources are not supported for Windows
+  pods.
+* **Resource Managers:** The Topology Manager, Memory Manager and CPU Manager do not
+  align pods and containers based on pod-level resources as these resource managers 
+  don't currently support pod-level resources.
+* **In-Place Resize:** In-place resize of pod-level resources is not supported.
+
 <!-- steps -->
 
 ## Create a namespace