KEP-1610: graduate ContainerResource to stable

keps/prod-readiness/sig-autoscaling/1610.yaml

@@ -1,3 +1,5 @@
 kep-number: 1610
 beta:
   approver: "@johnbelamaric"
+stable:
+  approver: "@johnbelamaric"

keps/sig-autoscaling/1610-container-resource-autoscaling/README.md

@@ -996,6 +996,20 @@ This through this both in small and large cases, again with respect to the
 
 No.
 
+###### Can enabling / using this feature result in resource exhaustion of some node resources (PIDs, sockets, inodes, etc.)?
+
+<!--
+Focus not just on happy cases, but primarily on more pathological cases
+(e.g. probes taking a minute instead of milliseconds, failed pods consuming resources, etc.).
+If any of the resources can be exhausted, how this is mitigated with the existing limits
+(e.g. pods per node) or new limits added by this KEP?
+
+Are there any tests that were run/should be run to understand performance characteristics better
+and validate the declared limits?
+-->
+
+No.
+
 ### Troubleshooting
 
 <!--

keps/sig-autoscaling/1610-container-resource-autoscaling/kep.yaml

@@ -12,16 +12,16 @@ approvers:
   - "@josephburnett"
   - "@gjtempleton"
 creation-date: 2020-02-18
-last-updated: 2023-02-02
+last-updated: 2024-01-15
 status: implementable
 
-latest-milestone: "1.27"
-stage: "beta"
+latest-milestone: "1.30"
+stage: "stable"
 
 milestone:
   alpha: "v1.20"
   beta: "v1.27"
-  stable: "v1.29"
+  stable: "v1.30"
 
 feature-gates:
   - name: HPAContainerMetrics