Documentation updates for Pod Level In Place resize Beta

content/en/docs/concepts/workloads/pods/pod-lifecycle.md

@@ -718,6 +718,7 @@ condition to `True` before sandbox creation and network configuration starts.
 ## Resizing Pods {#pod-resize}
 
 {{< feature-state feature_gate_name="InPlacePodVerticalScaling" >}}
+{{< feature-state feature_gate_name="InPlacePodLevelResourcesVerticalScaling" >}}
 
 Kubernetes supports changing the CPU and memory resources allocated to Pods
 after they are created. (For other infrastructure resources, you would need to
@@ -730,6 +731,9 @@ You can resize a Pod's container-level CPU and memory resources without recreati
 This is also called _in-place Pod vertical scaling_. This allows you to adjust resource
 allocation for running containers while potentially avoiding application disruption.
 
+If you have specified resources at the pod-level, you can also resize those in-place.
+For more details, see [Resize CPU and Memory Resources assigned to Pods](/docs/tasks/configure-pod-container/resize-pod-resources/).
+
 To perform an in-place resize, you update the Pod's desired state using the `/resize`
 subresource. The kubelet then attempts to apply the new resource values to the running
 containers. The Pod {{< glossary_tooltip text="conditions" term_id="condition" >}}

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

@@ -9,6 +9,10 @@ stages:
   - stage: alpha
     defaultValue: false
     fromVersion: "1.35"
+    toVersion: "1.35"
+  - stage: beta
+    defaultValue: true
+    fromVersion: "1.36"
 ---
 Enables the in-place vertical scaling of resources for a Pod (For example, changing a
 running Pod's pod-level CPU or memory requests/limits without needing to restart