Deploy the aws-ec2-security-group helm chart on Rancher

Question

Pulumi · Accepted Answer

To deploy the `aws-ec2-security-group` Helm chart on a Rancher-managed Kubernetes cluster using Pulumi, you will need to perform the following high-level tasks:

1. Set up the necessary Pulumi provider for Rancher to interact with your Kubernetes cluster.
2. Use the Rancher Pulumi provider to deploy the Helm chart to the cluster.

Below is a step-by-step guide on how to accomplish this task, along with a TypeScript program. First, we will set up the Rancher provider and then deploy the Helm chart.

### Setting up the Rancher Provider

To deploy to Rancher, we need to use the `rancher2` provider. This requires that you have configured Rancher with the appropriate access configurations including API tokens or certificates, and have Rancher properly managing the Kubernetes cluster where you want to install the Helm chart.

Here’s how you can establish a Pulumi program to deploy the `aws-ec2-security-group` helm chart on a Rancher cluster.

### Program Explanation

1. **Import dependencies**: We'll need to import Pulumi's `rancher2` package to interact with Rancher.

2. **Set up Rancher provider**: A `Provider` resource must be configured to define how to authenticate to your Rancher server.

3. **Deploy Helm chart**: Using `HelmChart` resource from the `rancher2` package, we can define our `aws-ec2-security-group` chart to be deployed on the cluster.

### Prerequisites

- Ensure that `@pulumi/rancher2` package is installed in your Pulumi project.
- Make sure you are authenticated to the Kubernetes cluster Rancher is managing.
- Make sure you have configured your Rancher API token, which will be used by the Pulumi Rancher2 provider.

### Pulumi TypeScript Program

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

// Step 1: Set up the Rancher provider to interact with your Rancher server.
const rancherProvider = new rancher2.Provider("rancherProvider", {
    // You should replace these values with your actual Rancher access configurations
    apiToken: "my-rancher-api-token",
    apiUrl: "https://my-rancher-server.com/v3",
});

// Step 2: Deploy the aws-ec2-security-group Helm chart.
const awsEc2SecurityGroupChart = new rancher2.HelmChart("aws-ec2-security-group-chart", {
    // You need to provide the correct chart name and the relevant repository URL where the chart is hosted
    chartName: "aws-ec2-security-group",
    repositoryUrl: "https://charts.my-helm-repo.com",
    // Specify the Rancher project ID in which the chart should be deployed
    projectId: "c-lwr2q:p-9fmwz",
    // Define any values that you want to override in the Helm chart
    values: {
        // Replace or add any values that you want to override in the Helm chart
        replicaCount: 2,
        // ...other overrides
    },
}, { provider: rancherProvider });

// Exporting the chart name to ensure it has been deployed.
export const chartName = awsEc2SecurityGroupChart.chartName;
```

This program defines the necessary Pulumi resources to deploy the `aws-ec2-security-group` helm chart on your Rancher-managed Kubernetes platform. Before running `pulumi up` to apply this program, make sure you have replaced placeholder strings for API tokens, URL, chart name, and repository URL with real values appropriate for your environment.

The `projectId` needs to correspond to the Rancher project where you want to deploy the Helm chart, and it typically follows the pattern `c-XXXXX:p-YYYYY`, where `c-XXXXX` is the cluster id and `p-YYYYY` is the project id.

The `values` field within the `HelmChart` resource allows you to provide any overrides for default values in the Helm chart. You should specify the chart values according to the `aws-ec2-security-group` chart's requirements. If there are no specific values you need to override, you can omit this field or provide an empty object.

After writing and saving your Pulumi program, you can deploy it using Pulumi CLI commands:

```shell
pulumi up
```

This command will preview the deployment and, upon confirmation, will proceed with the actual deployment to your Kubernetes cluster managed by Rancher. Once the deployment is complete, you can check the resources deployed in your Rancher Dashboard and the outputs returned by the Pulumi program.