Deploy the auto-discovery-cloud-aws helm chart on AWS EKS

Question

Pulumi · Accepted Answer

In order to deploy a Helm chart on AWS EKS using Pulumi, we will need to take the following steps:

1. **Setup an Amazon EKS cluster:** We'll begin by defining a new EKS cluster using the `eks.Cluster` Pulumi component. This high-level component bundles together the configuration of Kubernetes resources and AWS infrastructure that EKS requires.

2. **Deploy the Helm Chart:** After the EKS cluster is running, we will deploy the `auto-discovery-cloud-aws` Helm chart to the cluster. We are assuming that this Helm chart is available in a public or private Helm repository. We'll use the `kubernetes.helm.v3.Chart` resource to do this which represents a Helm chart in a Pulumi program.

Here's a TypeScript program accomplishing these steps. Ensure you have Pulumi and AWS CLI installed and configured before running this program.

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

// Step 1: Create an EKS cluster
const myCluster = new eks.Cluster("myCluster", {
    // Define the size and type of the cluster, these are example values.
    desiredCapacity: 2,
    minSize: 1,
    maxSize: 2,
    instanceType: "t2.medium",

// Optional: If you need to define specific version of Kubernetes, uncomment below
    // version: "1.18",
});

// Export the clusters' kubeconfig.
export const kubeconfig = myCluster.kubeconfig;

// Step 2: Deploy the Helm chart to the EKS cluster
// Note: We need to use a provider that understands that these resources belong to the EKS cluster that was just created.
const provider = new k8s.Provider("k8sProvider", {
    kubeconfig: myCluster.kubeconfig.apply(JSON.stringify),
});

// Deploy the Helm chart
const helmChart = new k8s.helm.v3.Chart("autoDiscoveryCloudAwsChart", {
    chart: "auto-discovery-cloud-aws",
    // Define the Helm repository where the chart is located
    // This is an example value, you will need to replace with the actual repo URL or name.
    // If the chart is in a public Helm repository, specify `repo` with the repository URL
    // If the chart is in a private Helm repository, additional configurations for repository access might be needed
    fetchOpts: {
        repo: "https://charts.example.com/"
    },
    // Optional: Any custom values for the Helm chart can be defined here
    // values: {
    //   serviceType: "LoadBalancer",
    // },
}, { provider });

// Export the Helm chart deployment status
export const chartStatus = helmChart.status;
```

Here's what each piece of code is doing:

- We create an EKS cluster with the `eks.Cluster` resource which abstracts away many of the complexities of setting up an EKS cluster.
- We output the `kubeconfig` which is needed to interact with the cluster using `kubectl` or any Kubernetes client library. This is sensitive information and typically it should be protected.
- We then create a Kubernetes provider with the `kubeconfig` of the newly-created EKS cluster.
- We define the Helm chart we want to deploy using the `k8s.helm.v3.Chart` resource. You'll have to specify the Helm chart details such as the chart name and optionally the `repo` where the chart is hosted, and any custom `values` you require for your Helm chart configuration.
- We export the status of the Helm chart using `chartStatus` to display the deployment outcome.

Before running this Pulumi program, you'll need to do the following:

1. Install Pulumi: Visit [Pulumi's Installation Guide](https://www.pulumi.com/docs/get-started/install/).
2. Configure AWS: Set up your AWS credentials via the [AWS CLI](https://docs.aws.amazon.com/cli/latest/userguide/cli-configure-quickstart.html) or through Pulumi's [AWS configuration](https://www.pulumi.com/registry/packages/aws/installation-configuration/).

To apply the Pulumi program, navigate to the directory with the `index.ts` file and run:

```sh
pulumi up
```

During the execution, Pulumi will display the status of resources being created and eventually provide you with a summary of the EKS cluster and Helm chart deployments. If the Helm chart `auto-discovery-cloud-aws` requires additional configuration or is hosted in a private repository, you will need to provide the corresponding `values` in the Helm chart definition or set up access to the repository as needed.