We will no longer update or support the Helm Chart for Single-Instance Kubernetes Deployments using OrientDB. This is because deploying Nexus Repository in containers with an embedded database has been known to corrupt the database under some circumstances. We strongly recommend that you use an external PostgreSQL database for Kubernetes deployments.
There is not nor do we anticipate their being a Helm chart available for single-instance Kubernetes deployments using PostgreSQL.
The only Helm chart we will support is the Helm Chart for Resilient AWS deployments using EKS, which allows you to deploy Nexus Repository in an EKS cluster as described in our resilient deployment options documentation.

Helm Charts for Sonatype Nexus Repository Manager 3

We provide Helm charts for two different deployment scenarios:

See the AWS Single-Instance Resiliency Chart if you are doing the following:

Deploying Nexus Repository Pro to an AWS cloud environment with the desire for automatic failover across Availability Zones (AZs) within a single region
Planning to configure a single Nexus Repository Pro instance within your Kubernetes/EKS cluster with two or more nodes spread across different AZs within an AWS region
Using an external PostgreSQL database (required)

See the Single-Instance OSS/Pro Helm Chart if you are doing the following:

Using embedded OrientDB (required)
Deploying either Nexus Repository Pro or OSS to an on-premises environment with bare metal/VM server (Node)
Deploying a single Nexus Repository instance within a Kubernetes cluster that has a single Node configured