Wondering if any of you can please explain:

oc logs defect-dojo-defectdojo-celery-worker-78dbb86b48-2rxn2
uid=1000640000(1000640000) gid=0(root) groups=0(root),1000640000
Waiting for database to be reachable [06/Jan/2021 13:40:58] INFO [dojo.models:3474] enabling audit logging

[06/Jan/2021 13:41:00] INFO [dojo.models:3474] enabling audit logging
Running a worker with superuser privileges when the
worker accepts messages serialized with pickle is a very bad idea!

If you really want to continue then you have to set the C_FORCE_ROOT
environment variable (but please think about this before you do).

User information: uid=1000640000 euid=1000640000 gid=0 egid=0

I get this when running using OpenShift restricted SCC. I'm not sure where it thinks superuser privileges are coming from?

Wondering if any of you can please explain:

oc logs defect-dojo-defectdojo-celery-worker-78dbb86b48-2rxn2
uid=1000640000(1000640000) gid=0(root) groups=0(root),1000640000
Waiting for database to be reachable [06/Jan/2021 13:40:58] INFO [dojo.models:3474] enabling audit logging

[06/Jan/2021 13:41:00] INFO [dojo.models:3474] enabling audit logging
Running a worker with superuser privileges when the
worker accepts messages serialized with pickle is a very bad idea!

If you really want to continue then you have to set the C_FORCE_ROOT
environment variable (but please think about this before you do).

User information: uid=1000640000 euid=1000640000 gid=0 egid=0

I get this when running using OpenShift restricted SCC. I'm not sure where it thinks superuser privileges are coming from?

I think it comes from gid=0 which means you belong to the root group. I have not yet found a good solution for it.

@madchap @alles-klar @ptrovatelli regardless of the celery issue (which we have resolved in our environment by using the C_FORCE_ROOT env variable) can you please approve the other changes so that required configuration parameters for OpenShift are added to the chart?

As you can see, we have a separate ticket open to resolve the celery "superuser privilege" conversation (and I believe I've identified the bug).

Added in the required rabbitmq KVs in values.yaml to utilise the podSecurityContext.enabled key added in Bitnami rabbitmq PR. This is needed to enable us to deploy to OpenShift via restricted SCC.