Test and make sure the default CR configuration works properly on OpenShift

[rm3l]

I just tried to use the operator locally against an OpenShift cluster (provided by ClusterBot), and noticed a few issues:

• PostgreSQL database in CrashLoopBackOff state, with the following logs (maybe the image we are using can't be run with a non-root user; I guess we should probably use a different image):

chmod: /var/lib/postgresql/data: Permission denied
chmod: /var/run/postgresql: Operation not permitted
The files belonging to this database system will be owned by user "1000690000".
This user must also own the server process.
The database cluster will be initialized with locale "en_US.utf8".
The default database encoding has accordingly been set to "UTF8".
The default text search configuration will be set to "english".
Data page checksums are disabled.
initdb: error: could not access directory "/var/lib/postgresql/data": Permission denied

• Backstage Pod, failing as well. Not sure from the logs if this was due to the lack of connection to the DB:

node:internal/modules/cjs/loader:1031
throw err;
^
Error: Cannot find module '/app/packages/backend'
at Function.Module._resolveFilename (node:internal/modules/cjs/loader:1028:15)
at Function.Module._load (node:internal/modules/cjs/loader:873:27)
at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:81:12)
at node:internal/main/run_main_module:22:47 {
code: 'MODULE_NOT_FOUND',
requireStack: []
}

Repro Steps

$ make install run
$ oc apply -f examples/postgres-secret.yaml
$ oc apply -f examples/bs1.yaml

---

TODO:

• Perhaps use the same PostgreSQL image as the one used by the Helm Chart. Check if this image is certified or not.

[rm3l]

Closing this issue as done. Everything is working on OpenShift and is being regularly checked.