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
Aggregated Discovery #3352
Comments
/sig api-machinery |
/milestone v1.25 |
Hello @Jefftree 👋, 1.25 Enhancements team here. Just checking in as we approach enhancements freeze on 18:00 PST on Thursday June 16, 2022. For note, This enhancement is targeting for stage Here's where this enhancement currently stands:
Looks like for this one, we would just need to get the open KEP PR #3364 merged by the Enhancements Freeze. For note, the status of this enhancement is marked as |
Hello @Jefftree 👋, just a quick check-in again, as we approach the 1.25 enhancements freeze. Please plan to get the open KEP PR merged before enhancements freeze on Thursday, June 23, 2022 at 18:00 PM PT. For note, the current status of the enhancement is at |
With KEP PR #3364 merged now, the enhancement is ready for the upcoming Enhancements Freeze. For note, the status is now marked as |
Hello @Jefftree 👋, 1.25 Release Docs Shadow here. This enhancement is marked as ‘Needs Docs’ for the 1.25 release. Please follow the steps detailed in the documentation to open a PR against the dev-1.25 branch in the k/website repo. This PR can be just a placeholder at this time and must be created by August 4. Also, take a look at Documenting for a release to familiarize yourself with the docs requirement for the release. Thank you! |
Hi @Jefftree, Enhancements team here again 👋 Checking in as we approach Code Freeze at 01:00 UTC on Wednesday, 3rd August 2022. Please ensure that the following items are completed before the code-freeze:
Currently, the status of the enhancement is marked as Thanks :) |
Hey @Jefftree , reaching out again as we approach Code Freeze at 01:00 UTC on this Wednesday i.e 3rd August 2022. The status of the enhancement is still marked as |
Hello, we will be dropping this enhancement for 1.25. Thanks! |
Thanks for the update @Jefftree ! I have marked this enhancement as |
If you're moving forward with this, please update the kep.yaml that just merged as it has milestone 1.25 still :) |
/milestone v1.26 |
@deads2k: Can not set label tracked/yes: Must be member in one of these teams: [release-team-enhancements release-team-leads] 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. |
/milestone v1.28 |
Spoke with Jefftree. Letting this soak in beta for another release. /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:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
/label lead-opted-in |
Hello @Jefftree 👋, 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 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 |
@meganwolf0 #4472 has been merged |
With all the requirements fulfilled this enhancement is now marked as tracked for the upcoming enhancements freeze 🚀 |
Hi @Jefftree! Congratulations on a stable release in 1.30! Please remember to open a docs placeholder PR this week -- even if you have no functionality updates, you need to update feature flags from |
Hi @Jefftree, 👋 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. |
Hey again @Jefftree 👋 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: With this, it is now marked as Also, please let me know if there are other PRs in k/k we should be tracking for this KEP. |
/remove-lifecycle stale |
Hello @Jefftree 👋, Enhancements team here. With all the implementation(code related) PRs merged as per the issue description:
This enhancement is now marked as |
Enhancement Description
One-line enhancement description (can be used as a release note): Aggregated Discovery
Kubernetes Enhancement Proposal: KEP
Discussion Link:
Primary contact (assignee): @Jefftree
Responsible SIGs: SIG API Machinery, SIG CLI
Enhancement target (which target equals to which milestone):
Alpha
k/enhancements
) update PR(s):k/k
) update PR(s):Beta
k/enhancements
) update PR(s): KEP-3352 Aggregated Discovery to Beta #3722k/k
) update PR(s):k/website
) update(s): Doc update for KEP-3352 Aggregated Discovery website#40024Stable
k/enhancements
) update PR(s): KEP-3352: Aggregated Discovery to GA #4472k/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: