Is there no risk of DB corruption even if the nexus repository oss version, which uses the H2 database as the embedded database, is used in a kubernetes environment?

Sonatype Nexus Repository
1

I am using the oss version of the nexus repository in a kubernetes environment.
Previously, the following web page stated that using the oss version of the embedded DB, orientDB, in combination with a kubernetes environment was deprecated due to the risk of the DB being corrupted.
https://help.sonatype.com/en/database-options.html
However, in recent versions, the oss version of the DB has changed from OrientDB to H2, and the above site no longer mentions the risk of DB corruption when using the nexus oss version in a kubernetes environment.
Since the embedded DB has been changed to H2 in recent versions of the nexus repository oss, has the risk of DB corruption been eliminated when using it in a kubernetes environment?

2

While H2 is more stable than Orient in our experience the same risk exists.

3

Thank you for your response. Is the risk of H2 only present when using K8s? Can the risk of database damage be completely avoided by using EC2?

4

With EC2 you’d want to make sure the services shuts down rather than is killed. Probably if you’re using a service this will happen.

You should also ensure that you create a task to backup the database, unlike OrientDB both SQL databases can produce a consistent backup while the system is running.