-
Notifications
You must be signed in to change notification settings - Fork 12
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
[Epic Blob-CSI] Implement the gatekeeper policies for PVs v.s. PVCs #1006
[Epic Blob-CSI] Implement the gatekeeper policies for PVs v.s. PVCs #1006
Comments
@cboin1996 & @bsewp045 - deferring this for 2 weeks to make room for documentation issues as per sprint planning discussion. |
On #1001 this is marked as completed (checked off), but this issue is still open. Should the issue be closed or was it checked off by mistake? |
Collin, please verify the status of this issue and action as required |
Based on the PR written, the GK policy was written to bind Protb PVs to Protb PVCs. The blob-csi controller dynamically provisions PVs and PVCs with the protb classification label and binds them together. There is no case of a user manually trying to bind PV to PVC. |
After talking to Collin, we've decided it would be nice to have this as a security measure to ensure a last line of defense if a user somehow is able to manually bind PV to PVC. This is not a priority at the moment and will be placed in the backlog. |
No description provided.
The text was updated successfully, but these errors were encountered: