Wojciech Tyczynski

/label lead-opted-in /label tracked/yes /remove-lifecycle stale

SLOs we are working on should be those "key metrics": https://github.com/kubernetes/community/blob/master/sig-scalability/slos/slos.md We should think how to expose them better.

@kubernetes/sig-scalability-feature-requests

I'm fine with legacy/ and head/ for other reasons (e.g. responsiveness metric). But I don't understand why you need it for the purpose of this issue?

Ahh - that's what you meant. Yeah, though given that we only run older releases on 100-node tests, even if that would have no effect, it should still be fine...

Actually, I think that PR that was submitted wasn't exactly what we want. We should create head/ and legacy/ subdirectories within individual tests, as needed. Or rather, I would say...

Point (2) from original description is mostly done in #488 However, as discussed offline with @krzysied while this fixes kube-proxy issues, it still leads to much higher resource usage of...

With https://github.com/kubernetes/kubernetes/pull/77918 adjusting DNS resource limits will be possible. @krzysied - once we get out of regressions, it's an important thing to look at.

@mm4tt - you did a part of it (which is switching to deployments). Would you mind taking the other parts to (adjust dns limits and bundle service together with Deployment)?...

/remove-lifecycle stale /lifecycle frozen