Deploy the sonatype-nexus helm chart on Rancher

Question

Pulumi · Accepted Answer

To deploy the Sonatype Nexus Helm chart on Rancher using Pulumi, you need to perform the following steps:

1. **Set up Rancher**: You must have a Rancher server up and running, and you should configure `kubectl` to interact with the Kubernetes cluster managed by Rancher.

2. **Install Pulumi**: If you haven't already done so, [install Pulumi](https://www.pulumi.com/docs/get-started/install/) and set up your [Pulumi account](https://app.pulumi.com/).

3. **Write the TypeScript program**: You'll use Pulumi's Rancher2 provider to interact with Rancher and deploy the Helm chart. Make sure you have Rancher credentials set up for authentication (typically via environmental variables or the Pulumi configuration system).

Below, you'll find a Pulumi TypeScript program that deploys the Sonatype Nexus Helm chart on Rancher. The program assumes you have the appropriate permissions and configurations to deploy resources on your Rancher-managed Kubernetes cluster.

### Detailed Explanation

The program begins by importing the required packages. Pulumi's `@pulumi/rancher2` package is used to interact with Rancher, and `@pulumi/kubernetes` is the standard Kubernetes provider to deploy Helm charts.

The program will use the `rancher2.Cluster` class to interact with an existing cluster managed by Rancher. The resource for the cluster is instantiated, and the name of the cluster is passed, which is imperative for Pulumi to know which cluster to operate on. We won't be managing the cluster itself in this deployment, so ensure you reference an already running and properly configured cluster.

Next, a Helm Release is deployed using the Pulumi Kubernetes provider. We define the Sonatype Nexus Helm chart using the `Chart` class with relevant configuration parameters such as the chart name, version, and any values you want to customize.

Finally, we will export the cluster name and the Helm release name as stack outputs, which you can use to reference the deployed resources later on. These stack outputs are useful for accessing details about the deployment programmatically or from the Pulumi CLI after the program has run.

### Pulumi TypeScript Program

```typescript
import * as rancher2 from "@pulumi/rancher2";
import * as k8s from "@pulumi/kubernetes";
import * as pulumi from "@pulumi/pulumi";

const clusterName = "my-rancher-cluster"; // Replace with the name of your Rancher-managed cluster

// Establish a connection to an existing Rancher cluster
const cluster = new rancher2.Cluster(clusterName, {
    name: clusterName,
});

// Upon successful connection to the cluster, use the Pulumi Kubernetes provider to deploy the Helm chart
const nexusChart = new k8s.helm.v3.Chart("sonatype-nexus", {
    chart: "sonatype-nexus",
    version: "1.24.3", // Specify the version of the chart you wish to deploy
    fetchOpts: {
        repo: "https://sonatype.github.io/helm3-charts/", // Helm chart repository
    },
    values: {
        persistence: {
            enabled: true,
            storageSize: "10Gi", // Adjust storage size as needed
        },
        // Add more custom values for the Sonatype Nexus Helm chart here
    },
}, { provider: new k8s.Provider("k8s-provider", { kubeconfig: cluster.kubeConfigRaw }) });

// Export the cluster name and Helm release name, which can be used to reference the resources later on
export const rancherClusterName = clusterName;
export const sonatypeNexusHelmReleaseName = nexusChart.metadata.apply(m => m.name);

```

When running this program with Pulumi, it will deploy the Sonatype Nexus Helm chart on your Rancher-managed Kubernetes cluster. Remember to replace placeholder values, like `my-rancher-cluster`, with those specific to your environment.

After you've written this program:

- Run `pulumi up` in the directory containing your Pulumi program.
- Review the resource changes that Pulumi proposes to perform.
- Confirm the deployment to proceed, and Pulumi will manage the deployment process for you.

The program output will display the names of created resources, and because of the defined stack exports, you can retrieve your Kubernetes cluster and Helm release names from the Pulumi console or CLI.