chore(psql): add securityContext to run as nonRoot

[fty4]

Description

Run the psql for consumer and provider with securityontext as nonRoot container.

Additional information

• related to chore: add kyverno validation workflow #28 - will decrease kyverno nonRoot findings

---

Marco Lecheler [email protected] Mercedes-Benz Tech Innovation GmbH (ProviderInformation)

[fty4]

Also use1001 also as group id - that was already the case.

Also currently the postgresql does not startup:

mkdir: cannot create directory ‘/bitnami/postgresql/data’: Permission denied

[fty4]

Problem:

mkdir can not be executed because the directory /bitnami/postgresql is owned by root and user 1001 can not create data directory:

$ pwd
/bitnami/postgresql
$ ls -la .
total 16
drwxrwxr-x  4 root root 4096 Jul 20 16:04 .
drwxr-xr-x  3 root root 4096 Dec 16  2022 ..
drwxrwxr-x  3 root root 4096 Jul 20 16:04 conf
drwx------ 19 1001 root 4096 Jul 20 16:04 data

[fty4]

We do not need this change - the problem is that in bitnami postgresql 12.1.6 chart the initContainers is not correctly templated:

...
      initContainers:
      containers:
        - name: postgresql
...

Because it is not templated as empty array (initContainers: []) or better not included the kyverno policy will not recognise any nonRoot securityContext and fail.

When updating to the latest (12.7.1) bitnami postgresql the problem will not occur.
Therefore the in the edc chart the psql dependency should be updated - no change in the e2e-testing value file will be required.