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

Add metric for access mode for persistent volume claims #554

Closed
EmilyM1 opened this issue Oct 10, 2018 · 8 comments · Fixed by #673
Closed

Add metric for access mode for persistent volume claims #554

EmilyM1 opened this issue Oct 10, 2018 · 8 comments · Fixed by #673
Labels
kind/feature Categorizes issue or PR as related to a new feature.

Comments

@EmilyM1
Copy link

EmilyM1 commented Oct 10, 2018

Is this a BUG REPORT or FEATURE REQUEST?:
Feature

/kind feature

What happened:

What you expected to happen:

It would be helpful to be able to see access modes on persistent volume claims.

How to reproduce it (as minimally and precisely as possible):

Anything else we need to know?:

Environment:

  • Kubernetes version (use kubectl version):
  • Kube-state-metrics image version
@k8s-ci-robot k8s-ci-robot added the kind/feature Categorizes issue or PR as related to a new feature. label Oct 10, 2018
@brancz
Copy link
Member

brancz commented Oct 16, 2018

See my answer in #555 🙂 .

@chancez
Copy link
Member

chancez commented Oct 18, 2018

AccessMode is a field on the PV in the spec. (see #555). What one supports is providerSpecific, but the value itself is on the resource regardless, otherwise PVC controller couldn't find PVs that fulfill it.

@fejta-bot
Copy link

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/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 16, 2019
@brancz
Copy link
Member

brancz commented Jan 16, 2019

/remove-lifecycle stale

Please ignore my answer from above. I think having access modes exposed as metrics would be useful.

@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 16, 2019
@tariq1890
Copy link
Contributor

/reopen

@k8s-ci-robot k8s-ci-robot reopened this May 30, 2019
@k8s-ci-robot
Copy link
Contributor

@tariq1890: Reopened this issue.

In response to this:

/reopen

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.

@tariq1890
Copy link
Contributor

/close

@k8s-ci-robot
Copy link
Contributor

@tariq1890: Closing this issue.

In response to this:

/close

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
kind/feature Categorizes issue or PR as related to a new feature.
Projects
None yet
6 participants