Post-Deployment Steps for HA

Only available in Sonatype Nexus RepositoryTM Pro. Interested in a free trial? Start here.

After you have completed your high availability (HA) deployment, there are a few steps you must take before you can fully use Sonatype Nexus Repository in its new HA environment.

Configuring Docker Repositories

As outlined in System Requirements for High Availability Deployments, if you plan to use more than one Docker repository, you must use one of the following:

• An external load balancer (e.g., NGINX) as a reverse proxy
• A Docker Subdomain Connector to route traffic to each Docker subdomain

We highly recommend using one of these two methods. However, if you only plan to have one Docker repository and will use port connectors instead of one of the above methods, then you must do the following:

1. Create the Docker repository in Sonatype Nexus Repository and specify a port (see our Docker format documentation).
2. Fill out an Ingress for Docker YAML and a Docker Service YAML (samples provided below).
3. Apply the Ingress for Docker YAML first.
4. Apply the Docker Service YAML second.

The Ingress for Docker YAML exposes the Docker service so that it can be reached from outside the Kubernetes cluster (i.e., the service created by Docker Services YAML). The Docker Service YAML creates a Kubernetes service through which a Docker repository can be reached via an HTTP port.

Sample YAMLs can be found in the following locations:

Warning
The YAML files linked in this section are just examples and cannot be used as-is. You must fill them out with the appropriate information for your deployment to be able to use them.

• AWS

  • AWS Ingress for Docker Connector YAML
  • AWS Docker Service YAML

• Azure

  • Azure Ingress for Docker Connector YAML
  • Azure Docker Service YAML

• On-Prem

  • On-Prem Ingress for Docker Connector YAML
  • On-Prem Docker Service YAML

Rebuild Metadata Tasks

Note
The rebuild metadata tasks described in this section are an upgrade requirement for anyone upgrading to 3.48.0+ and are not specific to HA deployments. However, if you did not upgrade to 3.48.0 or 3.49.0, you will need to run these tasks after upgrading to Sonatype Nexus Repository 3.50.0 or later.

After your deployment, you will need to run a Task for each existing Apt, Helm, and Yum repository to rebuild their metadata:

• Apt - Rebuild Apt metadata for each Apt repository
• Helm - Rebuild Helm metadata for each Helm repository
• Repair - Rebuild Yum repository metadata (repodata) for each Yum repository