Deploy the scorpio-broker helm chart on Linode Kubernetes Engine

Question

Pulumi · Accepted Answer

Deploying a Helm chart on a Kubernetes cluster involves several steps. Pulumi makes this process straightforward by providing a set of packages and classes which abstract away much of the complexity. Below, we'll go through the steps to accomplish your task.

The process typically involves these steps:

1. Set up a Kubernetes cluster where your Helm chart will be deployed.
2. Install the Helm chart onto the Kubernetes cluster.

Since Linode Kubernetes Engine (LKE) service is not directly supported by Pulumi as of my last update, you'll first need to provision an LKE cluster using the Linode provider or Linode's own means. Afterward, you'll need to configure your `kubectl` to interact with the new Linode Kubernetes cluster. Once you have access to your LKE cluster with `kubectl`, you can use Pulumi to deploy Helm charts using the `kubernetes.helm.v3.Chart` class provided by Pulumi's Kubernetes provider.

Assuming you've already set up and have access to your LKE cluster, the following Pulumi program will deploy the "scorpio-broker" Helm chart to your cluster.

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

// Define the Helm chart version and repository details.
const chart = "scorpio-broker";
const chartVersion = "x.y.z"; // Substitute "x.y.z" with the actual chart version you want to deploy.
const chartRepo = "https://helm-repo-url/"; // Substitute "https://helm-repo-url/" with the actual Scorpio Broker Helm repository URL.

// Deploy the Scorpio Broker Helm chart to the existing LKE Kubernetes cluster.
const scorpioBrokerRelease = new k8s.helm.v3.Chart("scorpio-broker-release", {
    chart: chart,
    version: chartVersion,
    fetchOpts: {
        repo: chartRepo,
    },
    // If you have custom values you'd like to override, specify them here.
    // values: {
    //     key1: "value1",
    //     key2: "value2",
    // },
});

// Export the frontend service URL so we can easily access it.
export const frontendServiceUrl = scorpioBrokerRelease.getResourceProperty(
    "v1/Service", "scorpio-broker-frontend", "status"
).apply(status => `http://${status.loadBalancer.ingress[0].ip}`);
```

In the code above:

- We import the `@pulumi/kubernetes` package, which allows us to deploy resources to Kubernetes clusters.
- We define the Helm chart we wish to deploy (`scorpio-broker`) and specify the version and Helm repository URL.
- We create a new instance of `k8s.helm.v3.Chart` which represents the Helm chart deployment in Pulumi. The `chart` argument specifies what chart to install, `version` indicates which version of the chart we want, and `fetchOpts.repo` tells Pulumi where to fetch the chart from.
- Optionally, we can provide custom values to the Helm chart by setting the `values` field, which allows you to override default chart values.

After you've created this program, deploy it using Pulumi by running `pulumi up` inside the directory where the program lives. Make sure you have Pulumi installed and configured to use your Kubernetes context for LKE.

To understand more about deploying Helm charts with Pulumi, please visit the [official Pulumi documentation for the Helm Chart resource](https://www.pulumi.com/registry/packages/kubernetes/api-docs/helm/v3/chart/).

Remember to replace the placeholders in `chartVersion` and `chartRepo` with actual values that correspond to the scorpio-broker Helm chart you want to use. Additionally, the `frontendServiceUrl` export assumes that the Helm chart creates a single Service of type LoadBalancer with an external IP; adjust accordingly based on the actual resources created by the Helm chart.

Keep in mind that the configuration of `kubectl` to interact with an LKE cluster is outside the scope of Pulumi, and should be done using Linode's tools or services.