# How to deploy Sonatype Nexus CE to K8s? **URL:** \ **Category:** Best Practices\ **Tags:** nexus-repository, kubernetes, helm\ **Created:** [February 10, 2025, 2:32pm UTC](https://community.sonatype.com/t/how-to-deploy-sonatype-nexus-ce-to-k8s/14360 "2025-02-10T14:32:52Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![Marc\_Richter](https://yyz1.discourse-cdn.com/flex047/user_avatar/community.sonatype.com/marc_richter/32/3757_2.png) [@Marc\_Richter](https://community.sonatype.com/u/Marc_Richter)\ **Post date:** [February 10, 2025, 2:32pm UTC](https://community.sonatype.com/t/how-to-deploy-sonatype-nexus-ce-to-k8s/14360/1 "2025-02-10T14:32:52Z")
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](http://community.sonatype.com/t/sonatype-nexus-repository-oss-is-now-community-edition/14324)) 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? ---
**Author:** ![Marc\_Richter](https://yyz1.discourse-cdn.com/flex047/user_avatar/community.sonatype.com/marc_richter/32/3757_2.png) [@Marc\_Richter](https://community.sonatype.com/u/Marc_Richter)\ **Post date:** [February 18, 2025, 3:03pm UTC](https://community.sonatype.com/t/how-to-deploy-sonatype-nexus-ce-to-k8s/14360/2 "2025-02-18T15:03:16Z")
Really? Noone had this issue when deploying to K8s before? What’s your solution then - stick to v64.2.0? ---
**Author:** ![mpiggott](https://avatars.discourse-cdn.com/v4/letter/m/f0a364/32.png) [@mpiggott](https://community.sonatype.com/u/mpiggott)\ **Post date:** [February 18, 2025, 5:13pm UTC](https://community.sonatype.com/t/how-to-deploy-sonatype-nexus-ce-to-k8s/14360/3 "2025-02-18T17:13:04Z")
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. ---
**Author:** ![Marc\_Richter](https://yyz1.discourse-cdn.com/flex047/user_avatar/community.sonatype.com/marc_richter/32/3757_2.png) [@Marc\_Richter](https://community.sonatype.com/u/Marc_Richter)\ **Post date:** [February 19, 2025, 3:10pm UTC](https://community.sonatype.com/t/how-to-deploy-sonatype-nexus-ce-to-k8s/14360/4 "2025-02-19T15:10:17Z")
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 😉 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 ---
**Author:** ![mpiggott](https://avatars.discourse-cdn.com/v4/letter/m/f0a364/32.png) [@mpiggott](https://community.sonatype.com/u/mpiggott)\ **Post date:** [February 19, 2025, 4:38pm UTC](https://community.sonatype.com/t/how-to-deploy-sonatype-nexus-ce-to-k8s/14360/5 "2025-02-19T16:38:44Z")
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](https://github.com/sonatype/nexus-public/issues) ---
**Author:** ![Gordana\_Deleva](https://avatars.discourse-cdn.com/v4/letter/g/b2d939/32.png) [@Gordana\_Deleva](https://community.sonatype.com/u/Gordana_Deleva)\ **Post date:** [October 1, 2025, 2:29pm UTC](https://community.sonatype.com/t/how-to-deploy-sonatype-nexus-ce-to-k8s/14360/6 "2025-10-01T14:29:34Z")
Hi Marc, I’m facing the same issue when trying to install Nexus CE on Kubernetes — the service refuses to start without the license file. Have you managed to find a solution to this problem? Best regards, Gordana ---
**Author:** ![Maksym\_Troshyn](https://avatars.discourse-cdn.com/v4/letter/m/4da419/32.png) [@Maksym\_Troshyn](https://community.sonatype.com/u/Maksym_Troshyn)\ **Post date:** [February 27, 2026, 2:34pm UTC](https://community.sonatype.com/t/how-to-deploy-sonatype-nexus-ce-to-k8s/14360/7 "2026-02-27T14:34:07Z")
I found the workaround how to deploy nexus community with new helm chart. The workaround is described in issue [Fix nxrm-ha helm chart to allow deploy nexus community edition · Issue #926 · sonatype/nexus-public · GitHub](https://github.com/sonatype/nexus-public/issues/926)