Skip to content

04 · Store

Nexus Repository

Hosts container images and build artifacts the pipeline produces

  1. Code
  2. Build
  3. Scan planned
  4. Store
  5. Deploy
  6. Observe

What it does

Nexus Repository stores the artifacts a pipeline builds, acting as a self-hosted container registry and package repository that later deploy steps pull from.

How it runs here

Runs in the nexus namespace as a ClusterIP service reached through a single Traefik host, nexus.kei-space.com, which path-routes UI, REST API, Docker and Helm OCI traffic without separate ports per protocol. Image and artifact data lives on a two-replica Longhorn volume dedicated to this app, and it also proxies Maven and npm downloads for CI.

Connects to

Why I chose it

One registry for both OCI images and Helm charts keeps the pipeline's "where do artifacts land" answer in a single place instead of a registry plus a separate chart repo.