Sonatype Nexus Repository oss

  • Single source of truth for all of your components, binaries, and build artifacts.
  • Efficiently distribute parts and containers to developers.
  • Deployed at more than 100,000 organizations globally.

Get started

Sonatype Nexus Repository OSS

Sonatype Nexus Repository Documentation.

Using Nexus Repository

Using Mirrors for Repositories with Maven

Admin Credentials

The nexus url is set with default admin credentials with username as admin and password admin123.

IMPORTANT: It is highly recommended that you change the admin password on first login.

Nexus Service

The nexus service is available in namespace nexus3:

kubectl get service -n nexus3 nexus3-nexus-repository-manager

Using the Service

Outside the cluster

NOTE: The service does not configured with Public IP, please use Kubernetes Ingress to expose the service to outside world.

Create an ingress:

kind: Ingress
  name: nexus3
  namespace: nexus3
  - http:
      - path: /
        pathType: Prefix
            name: nexus3-nexus-repository-manager
              number: 8081

Get the application url and open it in the browser:

open "$(kubectl get ing -n nexus3 nexus3 -o=jsonpath='{.status.loadbalancer.ingress[0].ip}')"

Inside the Cluster

The nexus repository is always accessible within the cluster via the in cluster URL http://nexus3-nexus-repository-manager.nexus3.svc.cluster.local:8081/repository/maven-public/

With Tektoncd Tasks

If you wish to use the Nexus repository manager with Tekton, you can configure your Java applications to use the deployed nexus as its Maven Mirror using MAVEN_MIRROR_URL environment variable. The environment variable will point to the in cluster repository URL http://nexus3-nexus-repository-manager.nexus3.svc.cluster.local:8081/repository/maven-public/

You can check more details with the Tektoncd Maven Task.

Nexus Configuration

The nexus configuration properties are stored in a ConfigMap called nexus-repository-manager-properties in namespace nexus3. If you with to change any nexus configuration, update the ConfigMap and bounce the nexus3 pod.