Open stlaz opened 1 year ago
/sig auth /sig api /assign
@stlaz: The label(s) sig/api
cannot be applied, because the repository doesn't have them.
/sig api-machinery
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
/remove-lifecycle stale
Hello @stlaz 👋, 1.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 1.29 (correct me, if otherwise)
Here's where this enhancement currently stands:
implementable
for latest-milestone: 1.29
. KEPs targeting stable will need to be marked as implemented after code PRs are merged and the feature gates are removed.For this KEP, we would need to add/update the following:
implementable
in the kep.yaml
file.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!
Hi @stlaz , 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 #3927 will address the requirements. Let me know if I missed anything. Thanks!
Hello :wave: Indeed, #3927 should indeed address the requirements. I'm trying to move it forward but it's not yet clear if it'll make it in time.
With KEP PR https://github.com/kubernetes/enhancements/pull/3927 approved, the enhancement is ready for the enhancements freeze. The status is now marked as tracked for enhancement freeze
for 1.29. 🚀 Thank you!
Hey there @stlaz! :wave:, v1.29 Docs Lead here. Does this enhancement work planned for v1.29 require any new docs or modification to existing docs? If so, please follows 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 familiarize with the docs requirement for the release. Thank you!
Hi again @stlaz ! The deadline to open a placeholder PR against k/website for required documentation is this Thursday, 19 October. Could you please update me on the status of docs for this enhancement? Thank you!
Hello, Sorry for late reply. Unfortunately, due to external circumstances, we won't be able to deliver the work for the 1.29 milestone :disappointed:
Hi @stlaz, 1.29 Enhancements team here- thanks for letting us know, I'll remove this KEP from the tracking board. /milestone clear
/remove-label lead-opted-in
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
/remove-lifecycle stale
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
/remove-lifecycle stale
Hello @stlaz 👋, 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 stage alpha
for v1.32 (correct me, if otherwise)
Here's where this enhancement currently stands:
implementable
for latest-milestone: v1.32
.For this KEP, we would just need to update the following:
latest-milestone
needs to be updated to v1.32
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!
The PRR request should be handled by https://github.com/kubernetes/enhancements/pull/4896
@jenshu #4896 is merged.
@stlaz @enj thanks for updating the kep.yaml, I've updated the status to tracked for enhancements freeze
!
Can you also be sure to keep the issue description at the top updated with the correct release targets and such?
Hi @stlaz :wave:, I'm James Spurin, a 1.32 Docs Shadow. Great to meet you again.
Does this enhancement work planned for 1.32 require any new docs or modifications to the 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 familiarise with the docs requirement for the release.
Thank you!
Hey there @stlaz 👋 from the v1.32 Communications Team!
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 it is graduating.
To opt-in, let us know by opening 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 finalize the blog schedule.
Hi @stlaz :wave:,
Just a reminder to open a placeholder PR against dev-1.32 branch in the k/website repo for this (steps available here) for this KEP if it requires new or modifications to existing docs.
The deadline for this is Thursday Oct 24 at 18:00 PDT.
Thanks
James Spurin
draft doc PR: https://github.com/kubernetes/website/pull/48463
Hey again @stlaz 👋, v1.32 Enhancements team here.
Just checking in as we approach code freeze at 02:00 UTC Friday 8th November 2024 / 19:00 PDT Thursday 7th November 2024.
Here's where this enhancement currently stands:
approved
and lgtm
labels applied) by the code freeze deadline. This includes tests.For this enhancement, it looks like the following PRs need to be merged before code freeze (and we need to update the Issue description to include all the related PRs of this KEP):
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!
/assign
Handling undecryptable resources
k/enhancements
) update PR(s): https://github.com/kubernetes/enhancements/pull/3927k/k
) update PR(s):k/website
) update PR(s):Please keep this description up to date. This will help the Enhancement Team to track the evolution of the enhancement efficiently.