Ramdomize pvc name cloudbeaver db

[nv6protect]

We are using single namespace déployment and we ran into an issue with cloudbeaver.
It uses a pvc name for the postgresql database : data-cloudbeaver-db-0.

When an another user start a new instance of cloudbeaver it tries to create the same name pvc.

It is possible to randomize this pvc ?

[olevitt]

We could also get rid of persistance for cloudbeaver as it's mostly stateless anyway (user would lost the connections they added and any duckdb work but that's arguably okay ?)

[ihiverlet]

To this day, I think we already lose the connections and any duckdb work when uninstalling cloudbeaver.
I don't see why persistance is used for except storing some preferences. Hence I do not see the point in keeping it.

[nv6protect]

if for some reason cloudbeaver pod restart do we lose connections added if we work without database ?

[ihiverlet]

Currently, the connections are not stored in the postgresql database so I'll switch to using embedded h2 database if possible or, at least, remove the persistence on the postgresql.

I'll also configure a pvc to ensure the connection data is preserved on pod restart.