[cinder-csi-plugin] Add Support to readonly volumes

kubernetes / cloud-provider-openstack

Apache License 2.0

619 stars 610 forks source link

[cinder-csi-plugin] Add Support to readonly volumes #1169

Closed ramineni closed 3 years ago

ramineni commented 4 years ago

Is this a BUG REPORT or FEATURE REQUEST?: /kind feature

Uncomment only one, leave it on its own line:

/kind bug /kind feature

What happened: Currently there is no support of making volume readonly. This feature is to enable the same.

What you expected to happen:

How to reproduce it:

Anything else we need to know?:

Environment:

openstack-cloud-controller-manager(or other related binary) version:
OpenStack version:
Others:

ramineni commented 4 years ago

/assign

fejta-bot commented 3 years ago

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

ramineni commented 3 years ago

/remove-lifecycle stale

fejta-bot commented 3 years ago

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-contributor-experience at kubernetes/community. /lifecycle stale

fejta-bot commented 3 years ago

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-contributor-experience at kubernetes/community. /lifecycle rotten

ramineni commented 3 years ago

/remove-lifecycle rotten

fejta-bot commented 3 years ago

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-contributor-experience at kubernetes/community. /lifecycle stale

k8s-triage-robot commented 3 years ago

The Kubernetes project currently lacks enough active 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 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 rotten

ramineni commented 3 years ago

There is no support in OPenstack yet to specify ro flag from nova . Support might take time. So closing the issue for now.

ramineni commented 3 years ago

/remove-lifecycle rotten

ramineni commented 3 years ago

Will reopen once supported from Openstack side. /close

k8s-ci-robot commented 3 years ago

@ramineni: Closing this issue.

In response to [this](https://github.com/kubernetes/cloud-provider-openstack/issues/1169#issuecomment-903632850): >Will reopen once supported from Openstack side. >/close Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.