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

Extend metrics stability #3498

Closed
31 tasks done
logicalhan opened this issue Sep 7, 2022 · 38 comments
Closed
31 tasks done

Extend metrics stability #3498

logicalhan opened this issue Sep 7, 2022 · 38 comments
Assignees
Labels
sig/instrumentation Categorizes an issue or PR as relevant to SIG Instrumentation. stage/stable Denotes an issue tracking an enhancement targeted for Stable/GA status
Milestone

Comments

@logicalhan
Copy link
Member

logicalhan commented Sep 7, 2022

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 Sep 7, 2022
@logicalhan
Copy link
Member Author

/sig instrumentation

@k8s-ci-robot k8s-ci-robot added sig/instrumentation Categorizes an issue or PR as relevant to SIG Instrumentation. and removed needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. labels Sep 7, 2022
@logicalhan
Copy link
Member Author

/lead-opted-in

@logicalhan logicalhan added the lead-opted-in Denotes that an issue has been opted in to a release label Sep 7, 2022
@dashpole
Copy link
Contributor

dashpole commented Sep 8, 2022

/assign @logicalhan

@dashpole dashpole added the stage/alpha Denotes an issue tracking an enhancement targeted for Alpha status label Sep 8, 2022
@rhockenbury
Copy link

/milestone v1.26

@k8s-ci-robot k8s-ci-robot added this to the v1.26 milestone Sep 11, 2022
@rhockenbury rhockenbury added the tracked/yes Denotes an enhancement issue is actively being tracked by the Release Team label Sep 20, 2022
@ruheenaansari34
Copy link

Hello @logicalhan 👋, 1.26 Enhancements team here.

Just checking in as we approach enhancements freeze on 18:00 PDT on Thursday 6th October 2022.

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

Here's where this enhancement currently stands:

  • KEP file using the latest template has been merged into the k/enhancements repo.
  • KEP status is marked as implementable
  • KEP has a updated detailed test plan section filled out
  • KEP has up to date graduation criteria
  • KEP has a production readiness review that has been completed and merged into k/enhancements.

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

The status of this enhancement is marked as at risk. Please keep the issue description up-to-date with appropriate stages as well. Thank you!

@logicalhan
Copy link
Member Author

@ruheenaansari34 I've updated the KEP to use the new template. Would you mind reassessing it? I also have a PRR reviewer actively conducting reviews.

@ruheenaansari34
Copy link

@logicalhan Thanks for updating it. Looks like all the requirements for the Enhancements freeze would be met once the PR is merged.

@ruheenaansari34
Copy link

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: 1.26
  • KEP readme has a updated detailed test plan section filled out
  • KEP readme has up to date graduation criteria.
  • KEP has a production readiness review that has been completed and merged into k/enhancements.

With all the KEP requirements in place and merged into k/enhancements, this enhancement is all good for the upcoming enhancements freeze. 🚀

The status of this enhancement is marked as tracked. Please keep the issue description up-to-date with appropriate stages as well. Thank you!

@rhockenbury
Copy link

Hi @logicalhan 👋,

Checking in as we approach 1.26 code freeze at 17:00 PDT on Tuesday 8th November 2022.

Please ensure the following items are completed:

  • All PRs to the Kubernetes repo that are related to your enhancement are linked in the above issue description (for tracking purposes).
  • All PRs are fully merged by the code freeze deadline.

Let me know if there's any PRs that we should be tracking that aren't mentioned in the issue description.

As always, we are here to help should questions come up. Thanks!

@cathchu
Copy link

cathchu commented Nov 2, 2022

Hello @logicalhan 👋 1.26 Release Docs shadow here!

This enhancement is marked as ‘Needs Docs’ for 1.26 release.
Please follow the steps detailed in the documentation to open a PR against dev-1.26 branch in the k/website repo. This PR can be just a placeholder at this time, and must be created by November 9. Also, take a look at Documenting for a release to familiarize yourself with the docs requirement for the release.

Thank you!

@logicalhan
Copy link
Member Author

This enhancement is marked as ‘Needs Docs’ for 1.26 release. Please follow the steps detailed in the documentation to open a PR against dev-1.26 branch in the k/website repo. This PR can be just a placeholder at this time, and must be created by November 9. Also, take a look at Documenting for a release to familiarize yourself with the docs requirement for the release.

Thank you!

This isn't a traditional feature, so it isn't actually guarded by a feature gate but one of the outputs of this work is documentation which I have already merged.

@marosset
Copy link
Contributor

/remove-label lead-opted-in
/remove-label tracked/yes
/label tracked/no
/milestone clear

@k8s-ci-robot k8s-ci-robot added tracked/no Denotes an enhancement issue is NOT actively being tracked by the Release Team and removed lead-opted-in Denotes that an issue has been opted in to a release labels Dec 14, 2022
@k8s-ci-robot k8s-ci-robot removed this from the v1.26 milestone Dec 14, 2022
@k8s-ci-robot k8s-ci-robot removed the tracked/yes Denotes an enhancement issue is actively being tracked by the Release Team label Dec 14, 2022
@logicalhan
Copy link
Member Author

/lead-opted-in

@ehashman ehashman removed the tracked/no Denotes an enhancement issue is NOT actively being tracked by the Release Team label Jan 19, 2023
@fsmunoz
Copy link

fsmunoz commented Mar 13, 2023

Hi @logicalhan 👋,

Checking in as we approach 1.27 code freeze at 17:00 PDT on Tuesday 14th March 2023.

Please ensure the following items are completed:

  • All PRs to the Kubernetes repo that are related to your enhancement are linked in the above issue description (for tracking purposes).
  • All PRs are fully merged by the code freeze deadline.

For this enhancement, it looks like there are no code changes.

Please let me know what other PRs in k/k I should be tracking for this KEP.

As always, we are here to help should questions come up. Thanks!

@mickeyboxell
Copy link

Hi @logicalhan, as @LukeMwila mentioned, please follow the steps detailed in the documentation to open a PR against dev-1.27 branch in the k/website repo. This placeholder PR must be created by today, March 16, and should be ready for review on Tuesday, March 21.

@Atharva-Shinde Atharva-Shinde removed this from the v1.27 milestone May 14, 2023
@Atharva-Shinde Atharva-Shinde removed tracked/yes Denotes an enhancement issue is actively being tracked by the Release Team lead-opted-in Denotes that an issue has been opted in to a release labels May 14, 2023
@logicalhan
Copy link
Member Author

/lead-opted-in

@logicalhan logicalhan added the lead-opted-in Denotes that an issue has been opted in to a release label May 22, 2023
@Atharva-Shinde
Copy link
Contributor

Atharva-Shinde commented May 23, 2023

Hello @logicalhan 👋, Enhancements team here.

Just checking in as we approach enhancements freeze on Thursday, 16th June 2023.

Is this enhancement staying to stage beta for v1.28? This enhancement is targeting stage stable

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.28
  • KEP readme has a updated detailed test plan section filled out
  • KEP readme has up to date graduation criteria
  • KEP has a production readiness review that has been completed and merged into k/enhancements.

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

  • Update kep.yaml with latest information.
  • Add response for this question in the Scalability questionnaire of the KEP readme.

The status of this enhancement is marked as at risk. Please keep the issue description up-to-date with appropriate stages as well. Thank you :)

@logicalhan logicalhan added stage/stable Denotes an issue tracking an enhancement targeted for Stable/GA status and removed stage/beta Denotes an issue tracking an enhancement targeted for Beta status labels May 30, 2023
@logicalhan
Copy link
Member Author

/milestone v1.28

@k8s-ci-robot k8s-ci-robot added this to the v1.28 milestone May 30, 2023
@Atharva-Shinde
Copy link
Contributor

Hey @logicalhan
With all the KEP requirements in place and merged into k/enhancements, this enhancement is all good for the upcoming enhancements freeze. 🚀

The status of this enhancement is marked as tracked. Please keep the issue description up-to-date with appropriate stages as well. Thank you :)

@VibhorChinda
Copy link

Hello @logicalhan 👋, 1.28 Docs Shadow here.

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

If so, please follows the steps here to open a PR against dev-1.28 branch in the k/website repo. This PR can be just a placeholder at this time and must be created before Thursday 20th July 2023.

Also, take a look at Documenting for a release to get yourself familiarize with the docs requirement for the release.

Thank you!

@Rishit-dagli
Copy link
Member

Hey @logicalhan , could you please create a docs PR even if it is a draft PR with no content yet against dev-1.28 branch in the k/website repo. The deadline to create this draft PR is Thursday 20th July 2023.

@Atharva-Shinde
Copy link
Contributor

Atharva-Shinde commented Jul 15, 2023

Hey again @logicalhan 👋

Here’s the enhancement’s state for the upcoming code freeze:

  • All the PRs that are related to your enhancement are linked in the above issue description (for tracking purposes). This includes code, tests, and documentation related PR/s.
  • All code related PR/s are merged or are in merge-ready state ( i.e they have approved and lgtm labels applied) by the code freeze deadline. This includes any tests related PR/s too.

For this enhancement, it looks like the following code related PR/s are open and they need to be merged or should be in merge-ready state before the code freeze commences :

These are the code related PR/s that I found on this KEP issue

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!

@VibhorChinda
Copy link

Hey @logicalhan , could you please create a docs PR even if it is a draft PR with no content yet against dev-1.28 branch in the k/website repo. The deadline to create this draft PR is Thursday 20th July 2023.
Thanks.

@Atharva-Shinde
Copy link
Contributor

Hey @logicalhan 👋 Enhancements Lead here,
With all the code related PRs merged as per the issue description, this enhancement is now tracked for v1.28 Code Freeze!
kubernetes/kubernetes#118689
kubernetes/kubernetes#119264
kubernetes/kubernetes#118820

@logicalhan
Copy link
Member Author

Hey @logicalhan , could you please create a docs PR even if it is a draft PR with no content yet against dev-1.28 branch in the k/website repo. The deadline to create this draft PR is Thursday 20th July 2023. Thanks.

kubernetes/website#42119

@VibhorChinda
Copy link

Hello @logicalhan 👋 please take a look at Documenting for a release - PR Ready for Review to get your PR ready for review before Tuesday 25th July 2023. Thank you!

@npolshakova
Copy link

/remove-label lead-opted-in

@k8s-ci-robot k8s-ci-robot removed the lead-opted-in Denotes that an issue has been opted in to a release label Aug 27, 2023
@logicalhan
Copy link
Member Author

/close

(as completed)

@k8s-ci-robot
Copy link
Contributor

@logicalhan: Closing this issue.

In response to this:

/close

(as completed)

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
sig/instrumentation Categorizes an issue or PR as relevant to SIG Instrumentation. stage/stable Denotes an issue tracking an enhancement targeted for Stable/GA status
Projects
Status: Net New
Status: Tracked
Status: Tracked
Development

No branches or pull requests