Considering that the database initialization is managed via flyway, the env var QUARKUS_HIBERNATE_ORM_DATABASE_GENERATION=update appended to data-index-postgresql deployments is wrong.

Now, every data-index-postgresql deployment is configured with the env var QUARKUS_HIBERNATE_ORM_DATABASE_GENERATION=update, which in some installations generates the side effect reported by the following support case: https://access.redhat.com/support/cases/#/case/04346665

Solution: the Operator must not generate that option, or generate the none option depending on wich is the default value for that property.

Note:  the QUARKUS_FLYWAY_MIGRATE_AT_START=true is being generated well as expected.