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
add ProcMount option #4265
Comments
replaces kubernetes/community#1934 |
/label lead-opted-in |
Hola @haircommander 👋, I am just checking in as we approach enhancements freeze on 18:00 PDT on Thursday 6th October 2023.. This enhancement is targeting stage 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 |
Sorry for the confusion @haircommander, this is actually currently |
Hello 👋, 1.29 Enhancements Lead here. #4266 is awaiting PRR approval. Please file an exception and once the PRR review is complete this should fulfill all the enhancement freeze requirements. Thanks! /milestone clear |
@haircommander, what's the “One-line enhancement description” for this KEP? |
@npolshakova https://groups.google.com/g/kubernetes-sig-release/c/emPOBgXxu0Q/m/JxEx-ZrcBgAJ?utm_medium=email&utm_source=footer
The exception is approved by v1.29 release team. However, we may miss the deadline again 🤣. |
@pacoxu It looks like this won't be making it into 1.29 from the slack discussion: https://kubernetes.slack.com/archives/C2C40FMNF/p1697033013866149?thread_ts=1696609849.513439&cid=C2C40FMNF |
/triage accepted |
/remove-label lead-opted-in |
@SergeyKanzhelev @mrunalp a little late but I have decided to update the KEP. can you PTAL and opt-in as discussed in sig node meeting? |
/stage beta |
Hello @haircommander 👋, Enhancements team here. Just checking in as we approach enhancements freeze on Friday, February 9th, 2024 at 02:00 UTC. This enhancement is targeting for stage 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 |
With all the requirements fulfilled this enhancement is now marked as tracked for the upcoming enhancements freeze 🚀 |
Hi @haircommander , 👋 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. |
Hello @haircommander 👋, v1.30 Docs Shadow here. Does this enhancement work planned for v1.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!
At a minimum, we'll need bumping Also, I edited the issue desc to update the target version :) - Beta release target (x.y): 1.29
+ Beta release target (x.y): 1.30 |
Hey again @haircommander 👋 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 PR is open and needs to be merged before code freeze: Also, please let me know if there are other PRs in k/k we should be tracking for this KEP. |
Hey @haircommander - code freeze is ~6 hours away! We still need kubernetes/kubernetes#123303 to merge before freeze or this will require an exception. |
Thanks for the heads up! I will file an exception |
Hello @haircommander 👋 Enhancements team 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 If you still wish to progress this enhancement in /milestone clear |
/milestone v1.30 |
@MaryamTavakkoli: 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:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
With the exception request being approved, this enhancement is now marked as /milestone v1.30 |
/stage alpha (retargeted at alpha) |
Enhancement Description
One-line enhancement description (can be used as a release note):
Kubernetes Enhancement Proposal:
Discussion Link:
Primary contact (assignee):
Responsible SIGs:
Enhancement target (which target equals to which milestone):
Alpha
k/enhancements
) update PR(s):k/k
) update PR(s):k/website
) update PR(s):Beta
k/enhancements
) update PR(s):k/k
) update PR(s):k/website
) update(s):Please keep this description up to date. This will help the Enhancement Team to track the evolution of the enhancement efficiently.
The text was updated successfully, but these errors were encountered: