You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: keps/sig-api-machinery/5116-streaming-response-encoding/README.md
+4-3Lines changed: 4 additions & 3 deletions
Original file line number
Diff line number
Diff line change
@@ -197,8 +197,9 @@ The tests will cover the following properties:
197
197
* Different content type JSON (default), Proto, CBOR, YAML.
198
198
* Different API kinds, eg ConfigMap, Pod, custom resources
199
199
200
-
In first iteration we expect we will overallocate the resources needed for apiserver to ensure passage,
201
-
however after the improvement is implemented we will tune down the resources to detect regressions.
200
+
The tests turned not only a great way to visualize the impact of the work, but also were able to catch [regression in Audit logs memory usage](https://github.com/kubernetes/kubernetes/issues/131720).
201
+
To ensure long term sustainability we propose to introduce a release blocking test, that will detect memory regression in apiserver handling large resources.
202
+
The test will run a known set of efficient requests and validate that apiserver memory didn't grow above certain threshold.
202
203
203
204
### Graduation Criteria
204
205
@@ -232,7 +233,7 @@ Via feature gates
232
233
233
234
234
235
-[X] Feature gate (also fill in values in `kep.yaml`)
0 commit comments