Skip to content

Operator 1.6 : Remove "AllowPrivilegeEscalation" or decouple "AllowPrivilegeEscalation" from "Privileged" #1403

@neelasha-09

Description

@neelasha-09

Hi Team,

While using OPR v1.6.1, we get the error seteuid: Operation not permitted due to cron binary unable to run.

zalando/spilo#562

We compared the old (1.5.0)and new operator (1.6.1) and observed the error is due to the allowPrivilegeEscalation: false under securityContext.

We see required either to remove the allowPrivilegeEscalation ( as in 1.5.0 ) or to decouple the allowPrivilegeEscalation from Privileged by having 2 different parameters:

Reference links below for the code:

Old OPR: 1.5.0 - Working

Privileged: &privilegedMode,

New OPR: 1.6.1 - cron error

AllowPrivilegeEscalation: &privilegedMode,

In conclusion, at least for OpenShift we need the parameter allowPrivilegeEscalation to be set as true and Privileged to be set as false

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions