Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow zero value for Sleep Action of PreStop Hook #4818

Open
2 of 4 tasks
sreeram-venkitesh opened this issue Aug 31, 2024 · 16 comments
Open
2 of 4 tasks

Allow zero value for Sleep Action of PreStop Hook #4818

sreeram-venkitesh opened this issue Aug 31, 2024 · 16 comments
Assignees
Labels
lead-opted-in Denotes that an issue has been opted in to a release sig/node Categorizes an issue or PR as relevant to SIG Node. stage/alpha Denotes an issue tracking an enhancement targeted for Alpha status
Milestone

Comments

@sreeram-venkitesh
Copy link
Member

sreeram-venkitesh commented Aug 31, 2024

Enhancement Description

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

@k8s-ci-robot k8s-ci-robot added the needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. label Aug 31, 2024
@sreeram-venkitesh
Copy link
Member Author

/sig node

@k8s-ci-robot k8s-ci-robot added sig/node Categorizes an issue or PR as relevant to SIG Node. and removed needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. labels Aug 31, 2024
@kubernetes kubernetes deleted a comment Aug 31, 2024
@kubernetes kubernetes deleted a comment Aug 31, 2024
@kubernetes kubernetes deleted a comment Aug 31, 2024
@kubernetes kubernetes deleted a comment Aug 31, 2024
@sreeram-venkitesh sreeram-venkitesh self-assigned this Sep 3, 2024
@SergeyKanzhelev
Copy link
Member

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

@k8s-ci-robot k8s-ci-robot added this to the v1.32 milestone Sep 24, 2024
@k8s-ci-robot k8s-ci-robot added the lead-opted-in Denotes that an issue has been opted in to a release label Sep 24, 2024
@kannon92 kannon92 moved this from Proposed for consideration to Considered for release in SIG Node 1.32 KEPs planning Sep 24, 2024
@kannon92
Copy link
Contributor

Based on @SergeyKanzhelev comments, I think we can move this to be "Considered For Release".

@impact-maker
Copy link

impact-maker commented Oct 1, 2024

Hello @sreeram-venkitesh 👋, Enhancements team here.

Just checking in as we approach enhancements freeze on 02:00 UTC Friday 11th October 2024 / 19:00 PDT Thursday 10th October 2024.

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

Here's where this enhancement currently stands:

  • KEP readme using the latest template has been merged into the k/enhancements repo.
  • KEP status is marked as implementable for latest-milestone: v1.32.
  • KEP readme has up-to-date graduation criteria
  • KEP has a production readiness review that has been completed and merged into k/enhancements. (For more information on the PRR process, check here). If your production readiness review is not completed yet, please make sure to fill the production readiness questionnaire in your KEP by the PRR Freeze deadline on Thursday, October 3rd, 2024 so that the PRR team has enough time to review your KEP.

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

  • KEP has a production readiness review that has been merged into k/enhancements.
    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!

@impact-maker impact-maker moved this to At risk for enhancements freeze in 1.32 Enhancements Tracking Oct 1, 2024
@sreeram-venkitesh
Copy link
Member Author

Thanks @impact-maker, the enhancements PR is already reviewed by the PRR team, I will resolve the comments and get it merged soon.

@sreeram-venkitesh
Copy link
Member Author

@impact-maker The KEP PR #4855 has been merged!

@sreeram-venkitesh
Copy link
Member Author

/stage alpha

@k8s-ci-robot k8s-ci-robot added the stage/alpha Denotes an issue tracking an enhancement targeted for Alpha status label Oct 3, 2024
@haircommander haircommander moved this from Considered for release to Tracked in SIG Node 1.32 KEPs planning Oct 3, 2024
@impact-maker impact-maker moved this from At risk for enhancements freeze to Tracked for enhancements freeze in 1.32 Enhancements Tracking Oct 4, 2024
@impact-maker
Copy link

@sreeram-venkitesh thanks! Everything looks good, I have updated the issue status to tracked for enhancements freeze

@chanieljdan
Copy link

Hi @sreeram-venkitesh 👋, 1.32 Release Docs Lead here.

Does this enhancement work planned for 1.32 require any new docs or modification to existing docs?

If so, please follows the steps here to open a PR against dev-1.32 branch in the k/website repo. This PR can be just a placeholder at this time and must be created before Thursday October 24th 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!

@sreeram-venkitesh
Copy link
Member Author

@chanieljdan This KEP would need docs! It needs the following (noting it down here for myself as well):

  • Document the new feature gate
  • Update the docs for the original Sleep Action docs to mention that people can use this feature gate to use the zero value.

I will open the PR soon! Thanks!

@chanieljdan
Copy link

@chanieljdan This KEP would need docs! It needs the following (noting it down here for myself as well):

  • Document the new feature gate
  • Update the docs for the original Sleep Action docs to mention that people can use this feature gate to use the zero value.

I will open the PR soon! Thanks!

Hi @sreeram-venkitesh 👋,

Thanks for your reply! Just a reminder to open a placeholder PR against dev-1.32 branch in the k/website repo for this (steps available here). The deadline for this is a week away at Thursday October 24, 2024 18:00 PDT.

Thanks,

Daniel

@sreeram-venkitesh
Copy link
Member Author

@chanieljdan I've opened the placeholder PR: kubernetes/website#48439

@wrkode
Copy link

wrkode commented Oct 24, 2024

👋 Hi there, William here from v1.32 Comms
We'd love for you to consider writing 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 30th Oct 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.

@sreeram-venkitesh
Copy link
Member Author

@wrkode This is a very small change, so I don't think this KEP would need a feature blog at this point in the release. Thanks a lot!

@wrkode
Copy link

wrkode commented Oct 28, 2024

Hi @sreeram-venkitesh, sounds good and thanks a million for the prompt feedback

@tjons
Copy link
Contributor

tjons commented Nov 4, 2024

Hello @sreeram-venkitesh 👋, Enhancements team here

With all the implementation(code related) PRs merged as per the issue description:

This enhancement is now marked as tracked for code freeze for the v1.32 Code Freeze!

Please note that KEPs targeting stable need to have the status field marked as implemented in the kep.yaml file after code PRs are merged and the feature gates are removed.

@tjons tjons moved this from Tracked for enhancements freeze to Tracked for code freeze in 1.32 Enhancements Tracking Nov 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lead-opted-in Denotes that an issue has been opted in to a release sig/node Categorizes an issue or PR as relevant to SIG Node. stage/alpha Denotes an issue tracking an enhancement targeted for Alpha status
Projects
Status: Tracked for code freeze
Status: Implemented
Development

No branches or pull requests

8 participants