How to deploy Sonatype Nexus CE to K8s?

Hi everyone,

we are using Sonatype Nexus OSS hosted in a Kubernetes Cluster, deployed using the Helm chart nexus-repository-manager from the repository at https://sonatype.github.io/helm3-charts/.

With the announcement by Sonatype about the transition from “Sonatype Nexus OSS” to “Sonatype Nexus Repository Community Edition” (see Sonatype Nexus Repository OSS is now Community Edition) and the nexus-repository-manager chart to cover up to version 64.2.0 only, we’d like to deploy a fresh instance of “Sonatype Nexus Repository Community Edition” to our Kubernetes Environment.
Analyzing the charts, this seems possible from the same repo, but we need to switch the chart from nexus-repository-manager to nxrm-ha instead.

This seems to provide the commercial version of “Sonatype Nexus” only, since the service refuses to start without providing a valid license file.

Can anyone please share details how to deploy “Sonatype Nexus Repository Community Edition” to some Kubernetes Cluster, please?

2 Likes

Really? Noone had this issue when deploying to K8s before? What’s your solution then - stick to v64.2.0?

With the embedded databases we found that kubernetes deployments had an increased chance of database corruption (as kubernetes may kill the pod) so the old charts were discontinued.

I passed along the fact the current chart requires a pro license but I don’t know what the timeline for making a change to it is.

Hey Matthew,

Thank you for the feedback!
We are fine with using the alternate charts, but as long as they don’t work for us, we have little chance to switch :wink:

So, I understand that this is unintended behavior of the chart - a.k.a “a Bug” - and that it will be fixed at some point.

Can we subscribe to a Bug tracker to get notified of the progress?

Best regards,
Marc

While the helm chart doesn’t live in this repository, it may make sense to file an issue at: https://github.com/sonatype/nexus-public/issues