search

kubernetes / enhancements

Enhancements tracking repo for Kubernetes
Apache License 2.0
3.4k stars 1.46k forks source link

CBOR Serializer #4222

Open benluddy opened 1 year ago

benluddy commented 1 year ago

Enhancement Description

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

benluddy commented 1 year ago

/sig api-machinery

npolshakova commented 1 year ago

Hello @benluddy, 1.29 Enhancements team here! Is this enhancement targeting 1.29? If it is, can you follow the instructions here to opt in the enhancements and make sure the lead-opted-in label is set so it can get added to the tracking board? Thanks!

deads2k commented 1 year ago

/milestone v1.29 /label lead-opted-in /stage alpha

rayandas commented 1 year ago

Hello @benluddy 👋, v1.29 Enhancements team here.

Just checking in as we approach enhancements freeze on 01:00 UTC, Friday, 6th October, 2023.

This enhancement is targeting for stage alpha for v1.29 (correct me, if otherwise)

Here's where this enhancement currently stands:

For this KEP, we would just need to update the following:

The status of this enhancement is marked as at risk for enhancement freeze. Please keep the issue description up-to-date with appropriate stages as well. Thank you!

rayandas commented 12 months ago

Hi @benluddy 👋🏽 checking in once more as we approach the 1.29 enhancement freeze deadline on 01:00 UTC, Friday, 6th October, 2023. The status of this enhancement is marked as at risk for enhancement freeze. It looks like updating and merging PR https://github.com/kubernetes/enhancements/pull/4223 will address most of the requirements. Let me know if I missed anything. Thanks.

rayandas commented 12 months ago

As https://github.com/kubernetes/enhancements/pull/4223 is merged, marking this as Tracked for Enhancements Freeze. 🚀 Thanks.

taniaduggal commented 11 months ago

Hey there @benluddy ! 👋, v1.29 Docs team shadow here. Does this enhancement work planned for v1.29 require any new docs or modifications to existing docs? If so, please follow the steps here to open a PR against dev-1.29 branch in the k/website repo. This PR can be just a placeholder at this time and must be created before Thursday, 19 October 2023. Also, take a look at Documenting for a release to get yourself familiarized with the docs requirement for the release. Thank you!

taniaduggal commented 11 months ago

Hey there @benluddy ! ,The deadline to open a placeholder PR against k/website for required documentation is Thursday, 19 October. Could you please update me on the status of docs for this enhancement? Thank you!

benluddy commented 11 months ago

Hi @taniaduggal, thanks for the reminder. I've opened a placeholder PR: https://github.com/kubernetes/website/pull/43557.

rayandas commented 11 months ago

Hey again @benluddy 👋, 1.29 Enhancements team here,

Just checking in as we approach code freeze at 01:00 UTC Wednesday 1st November 2023: .

Here's where this enhancement currently stands:

For this enhancement, looks like the following PRs are open and needs to be merged before code freeze.

The status of this KEP is currently at risk for Code Freeze.

Please update the issue description to include all the related PRs of this KEP under the alpha section in the issue description.

As always, we are here to help if any questions come up. Thanks!

a-mccarthy commented 11 months ago

Hi @benluddy, 👋 from the v1.29 Release Team-Communications! We would like to check if you have any plans to publish a blog for this KEP regarding new features, removals, and deprecations for this release.

If so, you need to open a PR placeholder in the website repository. The deadline will be on Tuesday 14th November 2023 (after the Docs deadline PR ready for review)

Here is the 1.29 calendar

benluddy commented 11 months ago

@rayandas Thanks. This will have to target a later release, it won't be ready for 1.29.

npolshakova commented 11 months ago

Hello @benluddy, 👋 1.29 Enhancements lead here,

Unfortunately, the implementation (code related) PR(s) associated with this enhancement is not in the merge-ready state by code-freeze and hence this enhancement is now removed from the 1.29 milestone.

If you still wish to progress this enhancement in 1.29, please file an exception request. Thanks!

/milestone clear

salehsedghpour commented 9 months ago

/remove-label lead-opted-in

deads2k commented 7 months ago

trying again for alpha in 1.30, with no KEP changes

/milestone v1.30 /label lead-opted-in

salehsedghpour commented 7 months ago

Hello @benluddy 👋, Enhancements team here.

Just checking in as we approach enhancements freeze on 02:00 UTC Friday 9th February 2024.

This enhancement is targeting for stage alpha for v1.30 (correct me, if otherwise)

Here's where this enhancement currently stands:

The status of this enhancement is marked as tracked for enhancement freeze. Please keep the issue description up-to-date with appropriate stages as well. Thank you!

kcmartin commented 7 months ago

Hi @benluddy,

👋 from the v1.30 Communications Team! We'd love for you to opt in to write a feature blog about your enhancement!

We encourage blogs for features including, but not limited to: breaking changes, features and changes important to our users, and features that have been in progress for a long time and are graduating.

To opt in, you need to open a Feature Blog placeholder PR against the website repository. The placeholder PR deadline is 27th February, 2024. Here's the 1.30 Release Calendar

drewhagen commented 7 months ago

Hello @benluddy 👋, 1.30 Docs Lead here.

Does this enhancement work planned for 1.30 require any new docs or modification to existing docs? If so, please follows the steps here to open a PR against dev-1.30 branch in the k/website repo. This PR can be just a placeholder at this time and must be created before Thursday February 22nd 2024 18:00 PDT.

Also, take a look at Documenting for a release to get yourself familiarize with the docs requirement for the release. Thank you!

benluddy commented 7 months ago

Hi @drewhagen, thanks! I've opened https://github.com/kubernetes/website/pull/45177 as a placeholder PR.

salehsedghpour commented 7 months ago

Hey again @benluddy 👋 Enhancements team here,

Just checking in as we approach code freeze at 02:00 UTC Wednesday 6th March 2024 .

Here's where this enhancement currently stands:

For this enhancement, it looks like the following PRs are open and need to be merged before code freeze (and we need to update the Issue description to include all the related PRs of this KEP):

With this, it is now marked as tracked for code freeze for the v1.30 Code Freeze!

Also, please let me know if there are other PRs in k/k we should be tracking for this KEP. As always, we are here to help if any questions come up. Thanks!

benluddy commented 7 months ago

/milestone clear

More work is needed to satisfy all of the alpha criteria. I intend to target 1.31 for alpha.

k8s-ci-robot commented 7 months ago

@benluddy: You must be a member of the kubernetes/milestone-maintainers GitHub team to set the milestone. If you believe you should be able to issue the /milestone command, please contact your Milestone Maintainers Team and have them propose you as an additional delegate for this responsibility.

In response to [this](https://github.com/kubernetes/enhancements/issues/4222#issuecomment-1980963175): >/milestone clear > >More work is needed to satisfy all of the alpha criteria. I intend to target 1.31 for alpha. Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.
sreeram-venkitesh commented 4 months ago

Hi @benluddy 👋, 1.31 Enhancements Lead here.

If you wish to progress this enhancement in v1.31, please have the SIG lead opt-in your enhancement by adding the lead-opted-in label and set the milestone to v1.31 before the Production Readiness Review Freeze.

/remove-label lead-opted-in

jpbetz commented 3 months ago

/label lead-opted-in /milestone v1.31

tjons commented 3 months ago

Hello @benluddy 👋, Enhancements team here.

Just checking in as we approach enhancements freeze on 02:00 UTC Friday 14th June 2024 / 19:00 PDT Thursday 13th June 2024.

This enhancement is targeting for stage alpha for 1.31 (correct me, if otherwise)

Here’s where this enhancement currently stands:

For this KEP, we would just need to complete the following:

The status of this enhancement is marked as at risk for enhancement freeze. Please keep the issue description up-to-date with appropriate stages as well.

If you anticipate missing enhancements freeze, you can file an exception request in advance. Thank you!

benluddy commented 3 months ago

Thanks @tjons!

Your kep.yaml file currently is marked as latest-milestone: 1.30.

https://github.com/kubernetes/enhancements/pull/4708 merged yesterday and updates this.

KEP has a production readiness review that has been completed and merged into k/enhancements.

I opened https://github.com/kubernetes/enhancements/pull/4722 to update the checklist. This KEP underwent PRR in the 1.29 cycle but did not graduate.

Merge the KEP readme using the latest template into the k/enhancements repo.

The template doesn't seem to have changed since this KEP's readme merged in https://github.com/kubernetes/enhancements/pull/4223. Is this tracking the two open PRs updating the readme?

Princesso commented 3 months ago

Hello @benluddy :wave:, 1.31 Docs Lead here. Does this enhancement work planned for 1.31 require any new docs or modification to existing docs? If so, please follow the steps here to open a PR against dev-1.31 branch in the k/website repo. This PR can be just a placeholder at this time and must be created before Thursday June 27, 2024 18:00 PDT. Also, take a look at Documenting for a release to get yourself familiarised with the docs requirement for the release. Thank you!

sreeram-venkitesh commented 3 months ago

Thanks @tjons!

Your kep.yaml file currently is marked as latest-milestone: 1.30.

4708 merged yesterday and updates this.

KEP has a production readiness review that has been completed and merged into k/enhancements.

I opened #4722 to update the checklist. This KEP underwent PRR in the 1.29 cycle but did not graduate.

Merge the KEP readme using the latest template into the k/enhancements repo.

The template doesn't seem to have changed since this KEP's readme merged in #4223. Is this tracking the two open PRs updating the readme?

Thanks @benluddy! Looks like all the requirements are met for this KEP. I'm marking this KEP as tracked for enhancements freeze! 🎉

a-mccarthy commented 3 months ago

Hi @benluddy, 👋 from the v1.31 Communications Team! We'd love for you to opt in to write a feature blog about your enhancement! Some reasons why you might want to write a blog for this feature include (but are not limited to) if this introduces breaking changes, is important to our users, or has been in progress for a long time and is graduating.

To opt in, let us know and open a Feature Blog placeholder PR against the website repository by 3rd July, 2024. For more information about writing a blog see the blog contribution guidelines.

Note: In your placeholder PR, use XX characters for the blog date in the front matter and file name. We will work with you on updating the PR with the publication date once we have a final number of feature blogs for this release.

benluddy commented 3 months ago

Hello @benluddy 👋, 1.31 Docs Lead here. Does this enhancement work planned for 1.31 require any new docs or modification to existing docs? If so, please follow the steps here to open a PR against dev-1.31 branch in the k/website repo. This PR can be just a placeholder at this time and must be created before Thursday June 27, 2024 18:00 PDT. Also, take a look at Documenting for a release to get yourself familiarised with the docs requirement for the release. Thank you!

Thanks for the reminder, @Princesso! I opened https://github.com/kubernetes/website/pull/46902 as a placeholder.

a-mccarthy commented 3 months ago

hi @benluddy, friendly reminder about the upcoming blog opt-in and placeholder deadline on July 3rd. Please open a blog placeholder PR if you are interested in contributing a blog.

tjons commented 2 months ago

Hey again @benluddy - 👋 Enhancements team here,

Just checking in as we approach code freeze at 02:00 UTC Wednesday 24th July 2024 / 19:00 PDT Tuesday 23rd July 2024. .

Here's where this enhancement currently stands:

For this enhancement, it looks like the following PRs are open and need to be merged before code freeze:

If you anticipate missing code freeze, you can file an exception request in advance.

Also, please let me know if there are other PRs in k/k we should be tracking for this KEP - thanks so much for being detail-oriented and adding them to the issue description already.

As always, we are here to help if any questions come up. Thanks!

jpbetz commented 2 months ago

/remove-milestone v1.31

EDIT: Per @benluddy, the implementation will not be ready in time for 1.31 code freeze

tjons commented 2 weeks ago

Hi, enhancements lead here - I inadvertently added this to the 1.32 tracking board 😀. Please readd it if you wish to progress this enhancement in 1.32.

/remove-label lead-opted-in

jpbetz commented 1 day ago

/label lead-opted-in /milestone v1.32

jpbetz commented 1 day ago

cc @benluddy to double me here- We do want this in for alpha in 1.32, correct?

benluddy commented 1 day ago

cc @benluddy to double me here- We do want this in for alpha in 1.32, correct?

Yes, thanks.