Skip to content

Commit b3184e4

Browse files
committed
add new question/answer
1 parent 66c5341 commit b3184e4

File tree

1 file changed

+14
-0
lines changed
  • keps/sig-autoscaling/1610-container-resource-autoscaling

1 file changed

+14
-0
lines changed

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

Lines changed: 14 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -996,6 +996,20 @@ This through this both in small and large cases, again with respect to the
996996

997997
No.
998998

999+
###### Can enabling / using this feature result in resource exhaustion of some node resources (PIDs, sockets, inodes, etc.)?
1000+
1001+
<!--
1002+
Focus not just on happy cases, but primarily on more pathological cases
1003+
(e.g. probes taking a minute instead of milliseconds, failed pods consuming resources, etc.).
1004+
If any of the resources can be exhausted, how this is mitigated with the existing limits
1005+
(e.g. pods per node) or new limits added by this KEP?
1006+
1007+
Are there any tests that were run/should be run to understand performance characteristics better
1008+
and validate the declared limits?
1009+
-->
1010+
1011+
No.
1012+
9991013
### Troubleshooting
10001014

10011015
<!--

0 commit comments

Comments
 (0)