The Wayback Machine - https://web.archive.org/web/20200829031727/https://github.com/kubernetes-sigs/kubespray/issues/5944
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

Dynamic Persistent volume Provisioning for ceph rbd provisioner #5944

Open
xin053 opened this issue Apr 13, 2020 · 4 comments
Open

Dynamic Persistent volume Provisioning for ceph rbd provisioner #5944

xin053 opened this issue Apr 13, 2020 · 4 comments

Comments

@xin053
Copy link

@xin053 xin053 commented Apr 13, 2020

What would you like to be added:

Enable Dynamic Persistent volume Provisioning for ceph rbd provisioner through adding "allowVolumeExpansion" parameter.

Why is this needed:

Dynamic Persistent volume Provisioning is necessary and ceph rbd support this.

@Miouge1
Copy link
Member

@Miouge1 Miouge1 commented Apr 20, 2020

Sounds like a good issue to start. Making allowVolumeExpansion configurable in roles/kubernetes-apps/external_provisioner/rbd_provisioner/templates/sc-rbd-provisioner.yml.j2

@xin053
Copy link
Author

@xin053 xin053 commented Apr 21, 2020

Actually there are several things to do:

  1. add allowVolumeExpansion in sc-rbd-provisioner.yml.j2
  2. change secret type from Opaque to kubernetes.io/rbd in secret-rbd-provisioner.yml.j2, for more information: https://kubernetes.io/zh/docs/concepts/storage/storage-classes/
  3. use hyperkube: #5422

in fact, I use ceph-csi-rbd to enable Dynamic Persistent volume Provisioning for ceph rbd provisioner

@fejta-bot
Copy link

@fejta-bot fejta-bot commented Jul 20, 2020

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

@fejta-bot
Copy link

@fejta-bot fejta-bot commented Aug 19, 2020

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

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 rotten

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
4 participants
You can’t perform that action at this time.