search

kubernetes / enhancements

Enhancements tracking repo for Kubernetes
Apache License 2.0
3.43k stars 1.48k forks source link

add ProcMount option #4265

Open haircommander opened 1 year ago

haircommander 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.

haircommander commented 1 year ago

replaces https://github.com/kubernetes/community/pull/1934 /sig node /sig auth

mrunalp commented 1 year ago

/label lead-opted-in

AnaMMedina21 commented 1 year ago

Hola @haircommander 👋, v1.29 Enhancements team here.

I am just checking in as we approach enhancements freeze on 18:00 PDT on Thursday 6th October 2023..

This enhancement is targeting stage beta 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 Tracked for Enhancements Freeze. Please keep the issue description up-to-date with appropriate stages as well. Thank you!

npolshakova commented 1 year ago

Sorry for the confusion @haircommander, this is actually currently At Risk for Enhancement Freeze until https://github.com/kubernetes/enhancements/pull/4266 is approved. We'll update the status once the PR goes in. Let me know if you have any questions- Thanks!

npolshakova commented 1 year ago

Hello 👋, 1.29 Enhancements Lead here. Unfortunately, this enhancement did not meet requirements for v1.29 enhancements freeze. Feel free to file an exception to add this back to the release tracking process.

https://github.com/kubernetes/enhancements/pull/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

sftim commented 1 year ago

@haircommander, what's the “One-line enhancement description” for this KEP?

pacoxu commented 1 year ago

@npolshakova https://groups.google.com/g/kubernetes-sig-release/c/emPOBgXxu0Q/m/JxEx-ZrcBgAJ?utm_medium=email&utm_source=footer

Your updated deadline to make any changes to your KEP is 18:00 PST Monday 9th October 2023.

The exception is approved by v1.29 release team. However, we may miss the deadline again 🤣.

npolshakova commented 1 year ago

@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

stlaz commented 11 months ago

/triage accepted

salehsedghpour commented 10 months ago

/remove-label lead-opted-in

haircommander commented 9 months ago

@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?

mrunalp commented 9 months ago

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

tjons commented 9 months ago

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 beta for 1.30 (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. Thank you!

tjons commented 9 months ago

With all the requirements fulfilled this enhancement is now marked as tracked for the upcoming enhancements freeze 🚀

Checksumz commented 8 months ago

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. The placeholder PR deadline is 27th February, 2024. Here's the 1.30 Release Calendar

Vyom-Yadav commented 8 months ago

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!

Does this enhancement work planned for v1.30 require any new docs or modification to existing docs?

At a minimum, we'll need bumping ProcMountType feature gate to beta in docs, so marking as Need Docs. If there are some logical changes, we'll need a PR for that too. Thanks!

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
tjons commented 8 months ago

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. As always, we are here to help if any questions come up. Thanks!

tjons commented 8 months ago

Hey @haircommander - code freeze is ~6 hours away! We still need https://github.com/kubernetes/kubernetes/pull/123303 to merge before freeze or this will require an exception.

haircommander commented 8 months ago

Thanks for the heads up! I will file an exception

salehsedghpour commented 8 months ago

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 v1.30 milestone.

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

/milestone clear

MaryamTavakkoli commented 8 months ago

/milestone v1.30

k8s-ci-robot commented 8 months ago

@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](https://github.com/kubernetes/enhancements/issues/4265#issuecomment-1981656311): >/milestone v1.30 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.
salehsedghpour commented 8 months ago

With the exception request being approved, this enhancement is now marked as tracked for code freeze.

/milestone v1.30

haircommander commented 7 months ago

/stage alpha

(retargeted at alpha)

sreeram-venkitesh commented 5 months ago

Hi @haircommander 👋, 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

sohankunkerkar commented 5 months ago

/stage beta

k8s-ci-robot commented 5 months ago

@sohankunkerkar: Can not set label lead-opted-in: Must be member in one of these teams: [release-team-enhancements release-team-leads sig-api-machinery-leads sig-apps-leads sig-architecture-leads sig-auth-leads sig-autoscaling-leads sig-cli-leads sig-cloud-provider-leads sig-cluster-lifecycle-leads sig-contributor-experience-leads sig-docs-leads sig-instrumentation-leads sig-k8s-infra-leads sig-multicluster-leads sig-network-leads sig-node-leads sig-release-leads sig-scalability-leads sig-scheduling-leads sig-security-leads sig-storage-leads sig-testing-leads sig-windows-leads]

In response to [this](https://github.com/kubernetes/enhancements/issues/4265#issuecomment-2148033179): >/stage beta >/label lead-opted-in 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-sigs/prow](https://github.com/kubernetes-sigs/prow/issues/new?title=Prow%20issue:) repository.
mrunalp commented 5 months ago

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

tjons commented 5 months ago

Hello @haircommander 👋, 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 beta 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!

sohankunkerkar commented 5 months ago

@tjons, this KEP has already undergone PRR reviews in the previous release. We were waiting for userns support, which wasn't available at that time. So from a PRR perspective, we are already covered.

tjons commented 5 months ago

OK, thanks! Updated to tracked for enhancement freeze 🚀

hacktivist123 commented 4 months ago

Hello @haircommander :wave:, 1.31 Docs Shadow here.

Does this enhancement work planned for 1.31 require any new docs or modification to existing docs? If so, please follows 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!

sohankunkerkar commented 4 months ago

/assign sohankunkerkar

a-mccarthy commented 4 months ago

Hi @sohankunkerkar,

👋 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.

Princesso commented 4 months ago

Hello @haircommander 👋, 1.31 Docs Shadow here.

Does this enhancement work planned for 1.31 require any new docs or modification to existing docs? If so, please follows 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!

Hi @haircommander , good day. Gentle reminder to open a Doc placeholder for beta updates to this enhancement before June 27th, 2024 which is the deadline for having a doc PR up. Thank you!

haircommander commented 4 months ago

@sohankunkerkar can you do that please?

sohankunkerkar commented 4 months ago

@sohankunkerkar can you do that please?

https://github.com/kubernetes/website/pull/46953

a-mccarthy commented 4 months ago

hello @haircommander @sohankunkerkar, 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 3 months ago

Hey again @haircommander - 👋 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. As always, we are here to help if any questions come up. Thanks!

sohankunkerkar commented 3 months ago

xref: https://github.com/kubernetes/kubernetes/pull/125259

tjons commented 3 months ago

Hello @haircommander 👋, 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 1.31 Code Freeze!

tjons commented 1 month 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