Deploy the nfs-provisioner helm chart on Kubernetes

Question

Pulumi · Accepted Answer

Deploying a Helm chart on a Kubernetes cluster using Pulumi can be achieved through the `@pulumi/kubernetes` package, which gives you access to Kubernetes resources, including Helm charts. In this specific case, we will deploy the NFS Provisioner Helm chart. The NFS Provisioner is an open-source application that can provision persistent volumes on a Kubernetes cluster when using NFS for storage.

Here's a Pulumi TypeScript program that deploys the NFS Provisioner Helm chart:

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

// Instantiate a Kubernetes Provider.
// The default config uses the current context from the local kubeconfig file.
const provider = new k8s.Provider("k8s-provider", {});

// Deploy the nfs-provisioner Helm chart.
const nfsProvisionerChart = new k8s.helm.v3.Chart("nfs-provisioner", {
  chart: "nfs-server-provisioner",
  // Specify where Helm can find the nfs-server-provisioner chart
  repo: "stable",
  // Values to pass to the Helm chart, could be adjusted based on requirements
  values: {
    persistence: {
        enabled: true,
        size: "10Gi" // The size of the persistent volume
    },
    storageClass: {
        defaultClass: true
    }
  },
  // Using the provider ensures that Pulumi uses the configured Kubernetes context
}, { provider: provider });

// Export the NFS Provisioner's service name
export const nfsProvisionerServiceName = nfsProvisionerChart.getResourceProperty("v1/Service", "nfs-provisioner", "metadata.name");
```
This program does the following:

1. It imports the necessary `@pulumi/kubernetes` package to interact with Kubernetes resources.
2. It creates a Kubernetes provider instance using the current context from the kubeconfig file that the Pulumi CLI automatically uses. If you have multiple kubeconfig contexts or you are running this in a CI/CD environment, you may need to configure the provider with the appropriate context or kubeconfig file content.
3. It deploys the NFS Provisioner Helm chart, specifying the chart's repository and name. The `values` section contains the configuration values for the Helm chart. These values can be adjusted as needed for the provisioner; for example, changing the size of the persistent volume or setting other parameters supported by the chart.
4. It uses the `getResourceProperty` function to retrieve the metadata.name property from the Service resource that the Helm chart will create. This value is then exported, which will be displayed as output when the Pulumi program is applied successfully.

Note: The code above assumes that the "nfs-server-provisioner" Helm chart is available in the "stable" Helm repository. At the time of writing this, the official stable repository may be deprecated; you might need to find an updated repository or chart source if that's the case. The example also assumes the required NFS server and storage setup are already configured.

To run this program:

1. Ensure that Node.js and Pulumi are installed on your machine.
2. Save this code to a file with a `.ts` extension, for example, `nfsProvisioner.ts`.
3. Run `npm install @pulumi/kubernetes` to install the required Pulumi Kubernetes package.
4. Run `pulumi up` to deploy the Helm chart to your Kubernetes cluster.

Pulumi will show you a preview of the resources that will be created, modified, or deleted. If everything looks correct, you can confirm the changes to proceed with the deployment. After a successful deployment, the exported value (`nfsProvisionerServiceName`) will be displayed, which indicates the Kubernetes Service name for the NFS Provisioner.