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

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.

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!

Yes - this is planned for 1.17

Great. I'll add it to the tracking sheet 馃憤

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.

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.

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

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!

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.

Awesome! Thank you @wojtek-t

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

/remove-milestone v1.17

Was this page helpful?
0 / 5 - 0 ratings