Skip to content

SELinux Profile Bindings don't seem to work #462

@tdeokar-code

Description

@tdeokar-code

In the daemonset object, when the customer specifies the selinux profile explicitly using securityContext->seLinuxOptions->type, the profile gets assigned as [expected.]
If the customer removes that part, the customer thought that using a security profile binding would be sufficient in order to have the profile injected automatically (by the mutating webhook the cutsomer assume).
But when the customer checks the pod specs the selinux type is empty and the container context is set to the default container_t.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    Status

    🆕 New

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions