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

osd: add privileged support (back) to blkdevmapper securityContext (work-around) #9191

Merged
merged 1 commit into from Nov 17, 2021

Commits on Nov 17, 2021

  1. osd: add privileged support (back) to blkdevmapper securityContext (w…

    …ork-around)
    
    The blockdevmapper securityContext was changed to request a minimal set of
    required capabilities for its operation and drop running as privileged.
    While the base change works and is valid in terms of the container's copy operation,
    it turns out that OpenShift may require some additional configuration not
    currently covered by the limited securityContext and the capabilities granted.
    
    To not break those OpenShift deployments, make the blkdevmapper securityContext
    listen to the ROOK_HOSTPATH_REQUIRES_PRIVILEGED flag again to set privileged mode.
    This flag is true on OpenShift deployments and running as privileged
    works around the (missing) configuration problem for now.
    To properly drop privileged completely some additional investigation needs
    to be done on OpenShift deployments without relying on privileged execution.
    
    Signed-off-by: Omar Pakker <Omar007@users.noreply.github.com>
    Omar007 committed Nov 17, 2021
    Copy the full SHA
    8f90558 View commit details
    Browse the repository at this point in the history