Deploy the neuvector helm chart on Rancher

Question

Pulumi · Accepted Answer

Deploying a Helm chart on Rancher involves several steps. Rancher simplifies Kubernetes cluster management and application deployment. To deploy Helm charts, Rancher provides a Catalog feature that we can use to add and manage Helm chart repositories.

Pulumi is capable of interfacing with Rancher to manage resources within it. To deploy the NeuVector Helm chart, we will first ensure we have a Kubernetes cluster managed by Rancher. Then, we'll add the Helm chart's repository as a Catalog to Rancher and then use Pulumi to deploy the NeuVector Helm chart to our cluster.

Below is a TypeScript program using Pulumi to deploy the NeuVector Helm chart on a Rancher-managed Kubernetes cluster. Please note that you would need to have Pulumi installed, configured with credentials for both the Kubernetes cluster and Rancher, and you would also need access to Rancher's API.

1. **Rancher2 Provider Setup**: This is necessary for Pulumi to interact with the Rancher API. You must ensure that `RANCHER_URL` and `RANCHER_TOKEN` are appropriately configured for the Rancher instance you want to interact with.

2. **Catalog V2**: This resource is used to configure a Helm chart repository in Rancher. We're using it to add the repository that contains the NeuVector Helm chart.

3. **App V2**: This resource tells Rancher to deploy a specific chart from the repository we previously added. It includes details such as release name, namespace, and any values you want to override in the Helm chart.

Here's the Pulumi program:

```typescript
import * as pulumi from '@pulumi/pulumi';
import * as rancher2 from '@pulumi/rancher2';

// Configure the Rancher2 provider
const provider = new rancher2.Provider('rancher', {
    apiUrl: process.env.RANCHER_URL,
    tokenKey: process.env.RANCHER_TOKEN,
});

// Add NeuVector's Helm chart repository as a Catalog in Rancher
const neuvectorCatalog = new rancher2.CatalogV2('neuvector-catalog', {
    name: 'neuvector',
    clusterId: 'cluster-id', // Replace with the actual cluster ID
    url: 'https://neuvector.github.io/neuvector-helm/', // The NeuVector Helm chart repo URL
    gitBranch: 'main', // The default branch of the Helm repo Git repository
}, { provider });

// Deploy the NeuVector Helm chart using the Catalog
const neuvectorApp = new rancher2.AppV2('neuvector-app', {
    name: 'neuvector',
    clusterId: 'cluster-id', // Replace with the actual cluster ID
    namespace: 'neuvector', // Ensure this namespace exists in your Rancher-managed cluster
    repoName: neuvectorCatalog.name,
    chartName: 'neuvector', // The name of the chart in the repository
    chartVersion: '1.0.0', // Replace with the desired chart version
    // values: Configuration values that override those provided in the Helm chart itself
    values: pulumi.output({
        // Provide any custom values here
    }),
}, { provider });

// Export the App deployment URL
export const neuvectorAppUrl = neuvectorApp.status.url;

```

### Explanation:

- We set up a Rancher provider to authenticate with the Rancher server.
- We add the NeuVector Helm chart repository to Rancher through a CatalogV2 resource with the Helm repository URL.
- We deploy the NeuVector Helm chart on the cluster by creating an AppV2 resource. This resource refers to the catalog, specifies the chart name, version, and can also contain additional values to configure NeuVector.
- Finally, we export the URL to access the deployed NeuVector application, which is exposed once the AppV2 resource is successfully deployed and running.

Make sure to replace `'cluster-id'` with the actual ID of the Kubernetes cluster managed by Rancher, and customize the `values` field with the specific configurations you require for NeuVector.

Please ensure you review and adapt this program to your specific Rancher setup and NeuVector configuration needs before running it.