[nexus3] is safe to upgrade?

[eirisdg]

Good morning.

Since Sonatype changed the database from OrientDB to H2, focusing the deployment on working in HA, those of us who use Nexus OSS are a bit confused. They released a Helm chart for HA in which you can only deploy Nexus with a license, and those of us who want to continue using OSS should not use it. In that sense, most of us here are using your chart.

That being said, the question is... is it safe to use Nexus OSS in Kubernetes considering the drawbacks that Sonatype indicates for updating using the embedded database? According to them, there is a risk of corruption...

Can't the H2 database be persisted in some way?

[stevehipwell]

@eirisdg AFAIK as far as persistence goes H2 is a straight swap for OrientDB. So if you were previously happy using OrientDB then I can't see an issue with using H2.

Can't the H2 database be persisted in some way?

It would be persisted in exactly the same way as OrientDB, via a PersistentVolume; so the important factor here is the CSI and how reliable it is. I always used EBS and the only issue I ever had was OrientDB corrupting itself when the volume ran out of space (so use S3 or at least a separate volume for the blob store), and even then I was able to recover without any data loss.

FYI migration from the legacy Deployment pattern to the StatefulSet pattern isn't automated but should be pretty straightforward for anyone with intermediate K8s knowledge.