PV health monitor

[NickrenREN]

Feature Description

• One-line feature description (can be used as a release note): mark the PVs if the underlying volumes are unhealthy to avoid data loss
• Primary contact (assignee): @NickrenREN
• Responsible SIGs: @kubernetes/sig-storage-feature-requests
• Design proposal link (community repo): PV monitoring proposal community#1484
• Link to e2e and/or unit tests:
• Reviewer(s) - (for LGTM) recommend having 2+ reviewers (at least one from code-area OWNERS file) agreed to review. Reviewers from multiple companies preferred:
  @msau42
  @gnufied
• Approver (likely from SIG/area to which feature belongs):
  @saad-ali
  @jsafrane
• Feature target (which target equals to which milestone):
  • Alpha release target (x.y) TBD
  • Beta release target (x.y) TBD
  • Stable release target (x.y) TBD

[NickrenREN]

/assign

[justaugustus]

This feature current has no milestone, so we'd like to check in and see if there are any plans for this in Kubernetes 1.12.

If so, please ensure that this issue is up-to-date with ALL of the following information:

• One-line feature description (can be used as a release note):
• Primary contact (assignee):
• Responsible SIGs:
• Design proposal link (community repo):
• Link to e2e and/or unit tests:
• Reviewer(s) - (for LGTM) recommend having 2+ reviewers (at least one from code-area OWNERS file) agreed to review. Reviewers from multiple companies preferred:
• Approver (likely from SIG/area to which feature belongs):
• Feature target (which target equals to which milestone):
  • Alpha release target (x.y)
  • Beta release target (x.y)
  • Stable release target (x.y)

Set the following:

• Description
• Assignee(s)
• Labels:
  • stage/{alpha,beta,stable}
  • sig/*
  • kind/feature

Once this feature is appropriately updated, please explicitly ping @justaugustus, @kacole2, @robertsandoval, @rajendar38 to note that it is ready to be included in the Features Tracking Spreadsheet for Kubernetes 1.12.

---

Please note that Features Freeze is tomorrow, July 31st, after which any incomplete Feature issues will require an Exception request to be accepted into the milestone.

In addition, please be aware of the following relevant deadlines:

• Docs deadline (open placeholder PRs): 8/21
• Test case freeze: 8/28

Please make sure all PRs for features have relevant release notes included as well.

Happy shipping!

P.S. This was sent via automation

[NickrenREN]

Sorry for the late reply @justaugustus .
We plan to add this to kubernetes-incubator/external-storage repo at first, so this is mostly out of tree, not tight to kubernetes release.

/stage alpha

[justaugustus]

@NickrenREN -- thanks for the note! Can you update the timeline on the feature description?

[NickrenREN]

@justaugustus sure, updated

[zparnold]

Hey there! @NickrenREN I'm the wrangler for the Docs this release. Is there any chance I could have you open up a docs PR against the release-1.12 branch as a placeholder? That gives us more confidence in the feature shipping in this release and gives me something to work with when we start doing reviews/edits. Thanks!

[msau42]

This feature is being developed outside of Kubernetes and I'm not sure if we would need to modify Kubernetes documentation for this