Update keps/sig-node/2837-pod-level-resource-spec/README.md

Co-authored-by: Adrian Moisey <[email protected]>

Author: ndixita

keps/sig-node/2837-pod-level-resource-spec/README.md

@@ -1484,14 +1484,14 @@ sig-autoscaling: (#132237)[https://github.com/kubernetes/kubernetes/issues/13223
 #### Cluster Autoscaler
 
 The Cluster Autoscaler uses resourcehelper.PodRequests to calculate Pod resource
-requirements for scaling decisions version 1.4.0. This automatically 
+requirements for scaling decisions in K8s version 1.33. This automatically 
 includes Pod-level resource requests when the PodLevelResources feature gate is 
 enabled, ensuring accurate node scaling and utilization calculations.
 
 #### VPA
 
 Collaboration with sig-autoscaling has been established to integrate support for
-VPA with Pod-level resources, slated for VPA 1.34. The changes to support pod-level 
+VPA with Pod-level resources, slated for VPA 1.5. The changes to support pod-level 
 resources in VPA will be worked on in two phases:
 * [Scoped for Beta] Phase 1 of Necessary changes
   The necessary changes include augmenting the recommendation algorithm to
@@ -1526,6 +1526,8 @@ major change in itself, full support for Windows will be addressed in future
 KEPs, beyond the scope of this KEP.
 
 #### [Future KEP Consideration in 1.35] Memory Manager
+Please note: This will be a separate feature, as the required changes are
+not trivial and warrant further discussion.
 
 The Memory Manager currently allocates memory resources at
 the container level through its
@@ -1545,6 +1547,8 @@ backward compatibility by continuing to use the existing Allocate method for
 container-level allocation scenarios
 
 #### [Future KEP Consideration] CPU Manager
+Please note: This will be a separate feature, as the required changes are
+not trivial and warrant further discussion.
 
 The Memory Manager currently allocates memory resources at
 the container level through its
@@ -1590,6 +1594,8 @@ Note: This is a prelimnary analysis, and we might have real usecases to support
   resources. We can re-visit this again during the GA planning cycle.
 
 #### [Future KEP Consideration] Topology Manager
+Please note: This will be a separate feature, as the required changes are
+not trivial and warrant further discussion.
 
 Currently, scope=pod aggregates resource requirements from a pod's individual
 containers to determine overall pod-level needs. With the introduction of Pod