> For the complete documentation index, see [llms.txt](https://developer.harness.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.harness.io/continuous-delivery/troubleshooting-and-resources/armory/general/integration-with-nexus.md).

# Integration with Nexus

### Introduction <a href="#introduction" id="introduction"></a>

The following instructions provide a sample configuration to integrate Spinnaker with Nexus as an artifact repository.

### Prerequisites <a href="#prerequisites" id="prerequisites"></a>

1. Nexus as an artifact repository2. Kubernetes Operator with Kustomize templates in a deployment.

### Instructions <a href="#instructions" id="instructions"></a>

In Operator, the following configuration change can be made under: `spec.spinnakerConfig.config.repository` to enable connection to the Nexus repository needed. Please ensure that the following values below are adjusted to match the repository's values:

* baseUrl\* repo\* nodeId\* username\* password

```
spec:
  spinnakerConfig:
    config:
      repository:
       nexus:
        enabled: true
        searches:
        - name: Armorytest # Example. Please name as necessary
          permissions:
            READ:
            - '[]'
            WRITE:
            - '[]'
          baseUrl: https://armory.io # Example. Please use the correct URL
          repo: testrepo 
          nodeId: testNodeID
          username: testuser
          password: testpassword
```

Please note that this is from preliminary testing and only to provide a lead on what the configuration may look like. Any issues related to Nexus may be filed through Spinnaker Github Issue Tracker as a New Issue/Feature with the OSS community<https://github.com/spinnaker/spinnaker/issues>