Performance and scale improvements to core infrastructure and clients to hit scale goals about enhancements HOT 13 CLOSED

Need release note for 1.4 but consists of significant performance improvements to scheduler, refinement of cluster performance at the 2000 node scale, CPU and memory improvements across the board, and a number of smaller fixes to components to streamline future improvements.

from enhancements.

@smarterclayton as this feature has been moved under 1.5 milestone, what is the actual status of it?

from enhancements.

We delivered across the board scheduler improvements in 1.4, continued to
refine cluster performance, and improve throughput of a set of metrics.

For 1.5 etcd3 is the signature feature (covered etcd v3 API storage backend)
#44. We will enable http2
for more efficient network usage, and we also anticipate delivering more
throughput and scheduler performance fixes to support that which should get
us another across the board increase in supported cluster size. Sig-scale
will be the primary lister of features.

On Thu, Sep 29, 2016 at 9:24 AM, Ihor Dvoretskyi [email protected]
wrote:

@smarterclayton https://github.com/smarterclayton as this feature has
been moved under 1.5 milestone, what is the actual status of it?

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#12 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABG_p2gZ71RZ1SsfRCnNZeLYr_MysRRnks5qu7vzgaJpZM4I9EAC
.

from enhancements.

For users wanting to remain on etcd2 for now, 1.5 will offer a way to do this?

from enhancements.

Yes, etcd3 will be default for new clusters but etcd2 will continue to be a
configurable option for the foreseeable future. Please add that comment
onto the etcd3 feature.

On Thu, Sep 29, 2016 at 10:43 AM, Mark Petrovic [email protected]
wrote:

For users wanting to remain on etcd2 for now, 1.5 will offer a way to do
this?

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#12 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABG_p5KYNjLnq16fL-bGDUk2txOhH9kaks5qu86TgaJpZM4I9EAC
.

from enhancements.

@wojtek-t

from enhancements.

@kubernetes/sig-api-machinery @kubernetes/sig-scalability can you clarify the actual state of the feature in 1.5?

from enhancements.

@smarterclayton @kubernetes/sig-api-machinery @kubernetes/sig-scalability any update on this?

from enhancements.

We are unlikely going to hit the 5k goals set, but I'm sure @wojtek-t has more details.

from enhancements.

Yes - we will definitely not announce 5k goal for 1.5 (it's not yet decided if we announce any increase, as we need etcd v3 to announce any improvement - and there is a meeting when the decision will be made about etcd v3 - how and when to launch it).

from enhancements.

This feature hasn't received the "exception" status for 1.5. Moving to the next milestone.

from enhancements.

/cc @jeremyeder

from enhancements.

Closing this to replace with other issues. Primary goal accomplished in 1.6

from enhancements.