Enhancements: Avoid serializing the same object independently for every watcher

Created on 19 Jul 2019 · 12Comments · Source: kubernetes/enhancements

Enhancement Description

One-line enhancement description (can be used as a release note): Avoid serializing the same object independently for every watcher.
Kubernetes Enhancement Proposal: KEP
Primary contact (assignee): wojtek-t
Responsible SIGs: sig-apimachinery, sig-scalability
Enhancement target (which target equals to which milestone):
- Alpha release target (1.16)
- Beta release target (1.17)
- Stable release target (1.18)

_Please to keep this description up to date. This will help the Enhancement Team track efficiently the evolution of the enhancement_

siapi-machinery siscalability stagstable

Source

wojtek-t

Most helpful comment

See the comment above (my second last comment):

We're already code-complete for that. And given it's purely implementational change, it doesn't require any docs.
Which mean that we seem to be completely done with it.

wojtek-t on 30 Oct 2019

👍2

All 12 comments

Hey there @wojtek-t -- 1.17 Enhancements lead here. I wanted to check in and see if you think this Enhancement will be graduating to alpha in 1.17?

The current release schedule is:

Monday, September 23 - Release Cycle Begins
Tuesday, October 15, EOD PST - Enhancements Freeze
Thursday, November 14, EOD PST - Code Freeze
Tuesday, November 19 - Docs must be completed and reviewed
Monday, December 9 - Kubernetes 1.17.0 Released

If you do, once coding begins please list all relevant k/k PRs in this issue so they can be tracked properly. 👍

Thanks!

mrbobbytables on 24 Sep 2019

Yes - this is planned for 1.17

wojtek-t on 24 Sep 2019

Great. I'll add it to the tracking sheet 👍

mrbobbytables on 24 Sep 2019

Given it's not a feature per-se (this is implementation detail, the change is invisible to use), this will go directly to GA. Changing the stage.

wojtek-t on 1 Oct 2019

We're already code-complete for that. And given it's purely implementational change, it doesn't require any docs.
Which mean that we seem to be completely done with it.

wojtek-t on 22 Oct 2019

Nice! Just for accounting purposes, was this the primary PR?
https://github.com/kubernetes/kubernetes/pull/81914

mrbobbytables on 22 Oct 2019

Yes - https://github.com/kubernetes/kubernetes/pull/81914 is the main one.
https://github.com/kubernetes/kubernetes/pull/84043 is some minor improvement on top of it.

wojtek-t on 23 Oct 2019

👍1

Hello @wojtek-t I'm 1.17 docs lead.

Does this enhancement (or the work planned for v1.17) require any new docs (or modifications to existing docs)? If not, can you please update the 1.17 Enhancement Tracker Sheet (or let me know and I'll do so)

If so, just a friendly reminder we're looking for a PR against k/website (branch dev-1.17) due by Friday, November 8th, it can just be a placeholder PR at this time. Let me know if you have any questions!

daminisatya on 30 Oct 2019

See the comment above (my second last comment):

We're already code-complete for that. And given it's purely implementational change, it doesn't require any docs.
Which mean that we seem to be completely done with it.

wojtek-t on 30 Oct 2019

👍2

Awesome! Thank you @wojtek-t

daminisatya on 30 Oct 2019

This KEP has been implemented and released in 1.17. Closing.

wojtek-t on 10 Dec 2019

❤1

/remove-milestone v1.17