Deploy the velero-notifications helm chart on Rancher

Question

Pulumi · Accepted Answer

To deploy the `velero-notifications` Helm chart on a Rancher-managed Kubernetes cluster using Pulumi, you'll go through a few steps. Firstly, ensure you have access to the Rancher cluster where you want the Helm chart to be deployed. You'll need the relevant access credentials and permissions.

Here's a rundown of how you'll use Pulumi to deploy the helm chart:

1. **Define the Rancher Cluster**: You have to specify the cluster where you'd like to deploy the Helm chart. In Pulumi, you'd typically use the `rancher2.Cluster` resource if you want to create a new cluster, but since we are deploying to an existing one, we'll need the cluster ID and other access details.

2. **Rancher Catalog**: Before deploying a Helm chart through Rancher, you need to have the catalog which contains the Helm chart added to Rancher. Sometimes this is already done for you, but if not, you may need to create a `rancher2.CatalogV2` resource which represents the collection of Helm charts you can deploy. This step isn't always necessary if you're deploying from a catalog that's already added to Rancher.

3. **Deploy the Helm Chart**: You will use the `rancher2.AppV2` (not shown in the provided resources, but it exists in the Rancher2 Pulumi provider) to manage the lifecycle of applications installed via Helm Charts in Rancher.

Below is a TypeScript example that could be used as a template. Please note that since the `velero-notifications` chart specifics like repository URL are not provided in your query, I will show you a general structure, which you can modify with the exact details:

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

// Assuming the Rancher cluster is already setup and you have the relevant configurations (clusterId, etc.)
const clusterId = "my-cluster-id"; // Replace with your actual cluster ID

// If the catalog containing `velero-notifications` is not already present in your Rancher setup,
// you should create a Catalog resource or find the catalog in which the chart is present.
// Below is an example of how to create a catalog if needed.
const catalog = new rancher2.CatalogV2("velero-notifications-catalog", {
    // Replace the URL with the chart's repository URL
    url: "https://charts.example.com/repositories/velero-notifications/",
    clusterId: clusterId,
});

// Deploy the velero-notifications helm chart
const veleroNotifications = new rancher2.AppV2("velero-notifications-app", {
    // Specify the name of the cluster where the app will be deployed
    clusterId: clusterId,
    // Specify the namespace where the app should be installed or created if it does not exist
    namespace: "velero-notifications-ns",
    // This should refer to the name of the chart
    chartName: "velero-notifications",
    // The name of the repository where the chart can be found - should exactly match the name 
    // of the catalog you want to deploy from. Possibly `catalog.name` from the previous resource.
    repoName: catalog.name,
    // The version of the Helm chart to deploy
    chartVersion: "1.0.0", // replace with the version you want to deploy
    // Values allows you to specify values for the helm chart akin to a values.yaml file
    values: pulumi.output({key: "value"}).apply(valuesJson => JSON.stringify(valuesJson)),
});

// Export the URL to access deployed app, you have to define how to get this based on your ingress or other components
export const url = pulumi.interpolate`http://your-specific-service-url.com`;

```

In the example above:
- Replace `my-cluster-id` with the cluster ID of your Rancher-managed cluster.
- If `velero-notifications` is in a catalog that is not yet added to Rancher, you'll need to create a new `CatalogV2` resource with its details. Omitted if the chart is already in a known catalog.
- The `AppV2` resource represents the Helm chart deployment. Specify the chart name, version, and values according to your needs.

Before running this code, you'd need:
- Pulumi CLI installed and configured for use with Rancher.
- Access to the Rancher instance with permissions to deploy applications.
- The specific details of the `velero-notifications` Helm chart repository.

After setting up the above Pulumi program, you can run `pulumi up` to deploy the Helm chart. Pulumi will communicate with Rancher to apply the desired configuration.