This repository has been archived by the owner on Oct 21, 2020. It is now read-only.
CephFS Provisioner: Add secret namespace support. #550
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What this PR does / why we need it:
Which issue this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)
format, will close that issue when PR gets merged): fixes #fixes #309.
Special notes for reviewer:
We can deploy cephfs-provisioner in a dedicated namepsace, e.g.
cephfs
, and configure it to store secrets in this dedicated namespace. Then cephfs provisioner will don't need CREATE|DELETE permission on any namespace.example deployment.yaml:
example role.yaml:
example rolebinding.yaml:
cc @wongma7 @rootfs