Deploy the ibm-websphere-liberty helm chart on Digital Ocean Kubernetes Service

Question

Pulumi · Accepted Answer

To deploy the `ibm-websphere-liberty` Helm chart on the Digital Ocean Kubernetes Service using Pulumi, you would need to create a Kubernetes cluster in Digital Ocean, and then use the Helm chart resource to deploy `ibm-websphere-liberty`.

Here's a step-by-step process written in TypeScript, broken down into segments for clarity:

1. **Create a Kubernetes cluster on Digital Ocean**: Use the `digitalocean.KubernetesCluster` resource from the Digital Ocean provider.
2. **Deploy the Helm chart to the cluster**: After the cluster is provisioned, use the `kubernetes.helm.sh/v3.Chart` resource from the Kubernetes provider to deploy the `ibm-websphere-liberty` Helm chart.

Below is a Pulumi program in TypeScript:

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

const name = "do-cluster";

// Step 1: Create a Kubernetes cluster on Digital Ocean
const cluster = new digitalocean.KubernetesCluster(name, {
    region: "nyc3",
    version: "latest",
    nodePool: {
        name: "default",
        size: "s-2vcpu-2gb",
        nodeCount: 2,
    },
});

// Step 2: Deploy the Helm chart to the cluster
// First, we need to use the kubeconfig from the created cluster to interact with it
const provider = new kubernetes.Provider(name, {
    kubeconfig: cluster.kubeConfigs[0].rawConfig,
});

// Now we can deploy the Helm chart using the Kubernetes provider instance
const ibmWebsphereLibertyChart = new kubernetes.helm.v3.Chart("ibm-websphere-liberty", {
    chart: "ibm-websphere-liberty",
    // Here you may specify the Helm repository if the chart is not in the default Helm repo
    // If the chart is in a private repository, you need to add `repo` argument with repository URL
    // repo: "https://charts.your-repo.com/"
    // You can specify the version of the chart if necessary
    // version: "x.x.x",
    // Values can be provided if required to customize the Helm chart releases
    // values: { },
}, { provider });

// Export the cluster's kubeconfig and the service URL if it's exposed via a LoadBalancer
export const kubeconfig = cluster.kubeConfigs[0].rawConfig;
export const serviceUrl = ibmWebsphereLibertyChart.getResourceProperty("v1/Service", "ibm-websphere-liberty", "status").apply(status => status.loadBalancer.ingress[0].ip);
```

Here's what each part of the program is doing:

- The `digitalocean.KubernetesCluster` resource is used to create a new Kubernetes cluster in the "nyc3" region with the latest available version of Kubernetes and a default node pool with 2 nodes of size "s-2vcpu-2gb".
- The `kubernetes.Provider` resource sets up the Pulumi Kubernetes provider with the kubeconfig from the Digital Ocean cluster, which allows Pulumi to manage resources in that cluster.
- The `kubernetes.helm.v3.Chart` resource deploys the `ibm-websphere-liberty` Helm chart onto the Kubernetes cluster. It uses the Kubernetes provider we set up earlier.
- The `export` statements make the kubeconfig and the IP of the LoadBalancer (if one is created by the chart) accessible outside of Pulumi for use with `kubectl` or in applications that need to communicate with the cluster.

Make sure you have Pulumi and the required CLI tools for Digital Ocean (`doctl`) set up. After running `pulumi up`, Pulumi will perform the provisioning steps described above.

The provided Helm chart must be available in a Helm repository that Pulumi can access. If it's a private repository or a custom one, you must provide the `repo` property with the correct URL value, and if authentication is required, the credentials must be configured accordingly.