KEP-NNNN: allow informers for getting a stream of data instead of chu…

…nking.

The kube-apiserver is vulnerable to memory explosion.
The issue is apparent in larger clusters, where only a few LIST requests might cause serious disruption.
Uncontrolled and unbounded memory consumption of the servers does not only affect clusters that operate in an
HA mode but also other programs that share the same machine.
In this KEP we propose a potential solution to this issue.

keps/sig-api-machinery/NNNN-watch-list/kep.yaml

@@ -0,0 +1,51 @@
+title: Allow informers for getting a stream of data instead of chunking
+kep-number: NNNN
+authors:
+ - "@sttts"
+ - "@p0lyn0mial"
+owning-sig: sig-api-machinery
+participating-sigs:
+ - sig-scalability
+status: provisional
+creation-date: 2022-01-14
+reviewers:
+ - "@wojtek-t"
+approvers:
+ - "@deads2k"
+ - "@lavalamp"
+
+##### WARNING !!! ######
+# prr-approvers has been moved to its own location
+# You should create your own in keps/prod-readiness
+# Please make a copy of keps/prod-readiness/template/nnnn.yaml
+# to keps/prod-readiness/sig-xxxxx/00000.yaml (replace with kep number)
+#prr-approvers:
+
+see-also:
+replaces:
+
+# The target maturity stage in the current dev cycle for this KEP.
+stage: alpha
+
+# The most recent milestone for which work toward delivery of this KEP has been
+# done. This can be the current (upcoming) milestone, if it is being actively
+# worked on.
+latest-milestone: "v1.24"
+
+# The milestone at which this feature was, or is targeted to be, at each stage.
+milestone:
+ alpha: "v1.24"
+ beta: "tbd"
+ stable: "tbd"
+
+# The following PRR answers are required at alpha release
+# List the feature gate name and the components for which it must be enabled
+feature-gates:
+ - name: TBD
+ components:
+ - kube-apiserver
+disable-supported: true
+
+# The following PRR answers are required at beta release
+metrics:
+ - my_feature_metric