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.

Sign up for GitHub

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

Jump to bottom

PV Health Monitor #1432

Open
9 tasks
xing-yang opened this issue Jan 5, 2020 · 118 comments
Open
9 tasks

PV Health Monitor #1432

xing-yang opened this issue Jan 5, 2020 · 118 comments
Assignees
@xing-yang @NickrenREN
Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. sig/storage Categorizes an issue or PR as relevant to SIG Storage. stage/beta Denotes an issue tracking an enhancement targeted for Beta status

Comments

@xing-yang
Copy link
Contributor

xing-yang commented Jan 5, 2020 •
edited
Loading

Enhancement Description

  • One-line enhancement description (can be used as a release note):
Provide a PV health monitor to watch the health status of volumes and mark it if a PV becomes unhealthy.
@k8s-ci-robot k8s-ci-robot added the needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. label Jan 5, 2020
@xing-yang
Copy link
Contributor Author

/sig storage

@k8s-ci-robot k8s-ci-robot added sig/storage Categorizes an issue or PR as relevant to SIG Storage. and removed needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. labels Jan 5, 2020
@xing-yang
Copy link
Contributor Author

/kind feature

@k8s-ci-robot k8s-ci-robot added the kind/feature Categorizes issue or PR as related to a new feature. label Jan 5, 2020
@xing-yang
Copy link
Contributor Author

/assign @xing-yang

@xing-yang
Copy link
Contributor Author

/assign @NickrenREN

@xing-yang
Copy link
Contributor Author

/milestone v1.18

@k8s-ci-robot
Copy link
Contributor

@xing-yang: 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 and have them propose you as an additional delegate for this responsibility.

In response to this:

/milestone v1.18

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.

@xing-yang
Copy link
Contributor Author

/stage alpha

@k8s-ci-robot k8s-ci-robot added the stage/alpha Denotes an issue tracking an enhancement targeted for Alpha status label Jan 5, 2020
@xing-yang
Copy link
Contributor Author

Hi @jeremyrickard, can you help add this feature to the milestone? We are targeting Alpha in 1.18. Thanks!

@jeremyrickard jeremyrickard added the tracked/yes Denotes an enhancement issue is actively being tracked by the Release Team label Jan 15, 2020
@jeremyrickard
Copy link
Contributor

Hey there @xing-yang,

Checking in to see if you're still on track for 1.18? It looks like the KEP still hasn't been merged. As a reminder, that will need to occur before the Enhancement Freeze (end of day, Pacific Time, on January 28th).

Thanks!!

@xing-yang
Copy link
Contributor Author

@jeremyrickard Yes, we are still trying to get it merged by 1/28. Thanks!

@jeremyrickard
Copy link
Contributor

@xing-yang congrats on getting the KEP merged! Updated you to tracked in the sheet!

@xing-yang
Copy link
Contributor Author

Thanks @jeremyrickard !

@kikisdeliveryservice
Copy link
Member

/milestone v1.18

@k8s-ci-robot k8s-ci-robot added this to the v1.18 milestone Jan 29, 2020
@VineethReddy02
Copy link

VineethReddy02 commented Feb 5, 2020 •
edited
Loading

Hello, @xing-yang, I'm 1.18 docs lead.
Does this enhancement work planned for 1.18 require any new docs (or modifications to existing docs)? If not, can you please update the 1.18 Enhancement Tracker Sheet (or let me know and I'll do so)
If so, just a friendly reminder we're looking for a PR against k/website (branch dev-1.18) due by Friday, Feb 28th, it can just be a placeholder PR at this time. Let me know if you have any questions!

@xing-yang
Copy link
Contributor Author

Hi @VineethReddy02, I'll submit a doc PR placeholder soon. Thanks!

@kikisdeliveryservice
Copy link
Member

Hi @xing-yang !

As a reminder that the Code Freeze is Thursday 5th March. Can you please link all the k/k PRs or any other PRs that should be tracked for this enhancement when available?

Thanks!
The 1.18 Enhancements Team

@NickrenREN
Copy link
Contributor

Hi, @kikisdeliveryservice ,
We have started coding for this, but this is mostly out of tree(out of k8s core repo). So we probably do not need to follow the release timeline strictly.
But of course, if we send out the PRs, we will link them here.
Thanks

@xing-yang
Copy link
Contributor Author

CSI Spec PR is submitted here: container-storage-interface/spec#415

@xing-yang
Copy link
Contributor Author

Hi @VineethReddy02, I think the doc for this feature will be in kubernetes-csi/docs repo, not in kubernetes website repo. Can you please remove the doc requirement for this feature from the tracking sheet? Thanks!

@xing-yang xing-yang mentioned this issue Feb 20, 2020
Closed
@kikisdeliveryservice
Copy link
Member

/milestone clear

@xing-yang
Copy link
Contributor Author

@rhockenbury We won't get the e2e tests ready by the KEP merge deadline. So we are moving this to 1.27.

@xing-yang xing-yang removed this from the v1.26 milestone Oct 5, 2022
@xing-yang xing-yang removed the lead-opted-in Denotes that an issue has been opted in to a release label Oct 5, 2022
@rhockenbury
Copy link

No problem. Thanks for the update.

/milestone clear
/label tracked/no
/remove-label tracked/yes

@k8s-ci-robot k8s-ci-robot added tracked/no Denotes an enhancement issue is NOT actively being tracked by the Release Team and removed tracked/yes Denotes an enhancement issue is actively being tracked by the Release Team labels Oct 6, 2022
@k8s-triage-robot
Copy link

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue or PR as fresh with /remove-lifecycle stale
  • Mark this issue or PR as rotten with /lifecycle rotten
  • Close this issue or PR with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jan 4, 2023
@xing-yang
Copy link
Contributor Author

/remove-lifecycle stale

@k8s-ci-robot k8s-ci-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jan 12, 2023
@xing-yang xing-yang added the lead-opted-in Denotes that an issue has been opted in to a release label Jan 12, 2023
@xing-yang xing-yang added this to the v1.27 milestone Jan 12, 2023
@marosset
Copy link
Contributor

Hello @xing-yang & @NickrenREN 👋, Enhancements team here.

Just checking in as we approach enhancements freeze on 18:00 PDT Thursday 9th February 2023.

This enhancement is targeting for stage beta for v1.27 (correct me, if otherwise)

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.27
  • 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 enhancement, it looks like once #3321 merges all the requirements will be met for a beta graduation in v1.27

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!

@marosset
Copy link
Contributor

Unfortunately, this exception hasn't satisfied all of the requirements by the v1.27 code freeze and will be removed from the milestone.

If you feel it is important to include this exception in v1.27 please consider filing an exception as outlined at https://github.com/kubernetes/sig-release/blob/master/releases/EXCEPTIONS.md

@marosset marosset moved this from At Risk to Removed From Milestone in 1.27 Enhancements Tracking Feb 10, 2023
@k8s-triage-robot
Copy link

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue as fresh with /remove-lifecycle stale
  • Close this issue with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label May 11, 2023
@Atharva-Shinde Atharva-Shinde removed tracked/no Denotes an enhancement issue is NOT 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
@xing-yang
Copy link
Contributor Author

/remove-lifecycle stale

@k8s-ci-robot k8s-ci-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label May 24, 2023
@xing-yang xing-yang removed this from the v1.27 milestone May 24, 2023
@k8s-triage-robot
Copy link

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue as fresh with /remove-lifecycle stale
  • Close this issue with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jan 21, 2024
@xing-yang
Copy link
Contributor Author

/remove-lifecycle stale

@k8s-ci-robot k8s-ci-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jan 21, 2024
@adampl
Copy link

adampl commented Jan 24, 2024

/lifecycle frozen

@k8s-ci-robot k8s-ci-robot added the lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. label Jan 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@xing-yang xing-yang

@NickrenREN NickrenREN

Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. sig/storage Categorizes an issue or PR as relevant to SIG Storage. stage/beta Denotes an issue tracking an enhancement targeted for Beta status
Projects
(Test board) Kubernetes 1.26 Enhancements Tracking
Status: No status
1.26 Enhancements Tracking
Status: Graduating
1.27 Enhancements Tracking
Status: Removed From Milestone
Milestone
No milestone
Development

No branches or pull requests