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

ScaleIO - decouple secret namspace from PVC for dynamic provisioning #51555

Closed
vladimirvivien opened this issue Aug 29, 2017 · 3 comments
Closed

ScaleIO - decouple secret namspace from PVC for dynamic provisioning #51555

vladimirvivien opened this issue Aug 29, 2017 · 3 comments
Labels
lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. sig/storage Categorizes an issue or PR as relevant to SIG Storage.

Comments

@vladimirvivien
Copy link
Member

vladimirvivien commented Aug 29, 2017 •
edited

Is this a BUG REPORT or FEATURE REQUEST?:

/kind feature

This feature is to be able to create a PVC where the referred secret object can be decoupled and be part of a different namespace. This allows the PVC to be in a different namespace which can be more restrictive than that of the secret for accessing the storage backend.
@k8s-github-robot k8s-github-robot added the needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. label Aug 29, 2017
@vladimirvivien vladimirvivien changed the title ScaleIO plugin should decouple ScaleIO - decouple secret namspace from PVC for dynamic provisioning Aug 29, 2017
@vladimirvivien
Copy link
Member Author

/sig storage

@k8s-ci-robot k8s-ci-robot added the sig/storage Categorizes an issue or PR as relevant to SIG Storage. label Aug 29, 2017
@k8s-github-robot k8s-github-robot removed the needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. label Aug 29, 2017
@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.

Prevent issues from auto-closing with an /lifecycle frozen comment.

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 11, 2018
@vladimirvivien
Copy link
Member Author

This was implemented in PR #54013

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. sig/storage Categorizes an issue or PR as relevant to SIG Storage.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@vladimirvivien @k8s-github-robot @k8s-ci-robot @fejta-bot