Deploy the teleport-operator helm chart on AWS EKS

Question

Pulumi · Accepted Answer

To deploy the `teleport-operator` Helm chart on AWS EKS using Pulumi, you'll need to follow several steps. I'll guide you through the process, and provide you with a fully functional Pulumi program in TypeScript.

Here are the key steps you will need to perform:
1. **Set up an EKS Cluster**: The `eks.Cluster` class from the `@pulumi/eks` package simplifies the process of creating an EKS cluster.
2. **Install the Helm Chart**: The `kubernetes.helm.v3.Chart` class from the `@pulumi/kubernetes` package allows you to deploy Helm charts.

Below is a Pulumi program that will create an Amazon EKS cluster and deploy the `teleport-operator` Helm chart onto it. Make sure you have Pulumi installed and configured with AWS credentials.

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

// Step 1: Create a new EKS Cluster
const cluster = new eks.Cluster("pulumi-eks-cluster", {
    instanceType: "t2.medium",
    desiredCapacity: 2,
    minSize: 1,
    maxSize: 2,
    storageClasses: "gp2",
    deployDashboard: false,
});

// Export the cluster's kubeconfig.
export const kubeconfig = cluster.kubeconfig;

// Step 2: Deploy Teleport Operator Helm Chart to EKS Cluster
// You will need to install the Pulumi Kubernetes provider to interact with the cluster.
const provider = new k8s.Provider("k8s-provider", {
    kubeconfig: cluster.kubeconfig,
});

const helmChart = new k8s.helm.v3.Chart("teleport-operator", {
    // Replace with the actual chart repository and name
    repo: "stable",
    chart: "teleport-operator",
    // Add any custom values you need to configure the chart.
    values: {/* ... */},
    // Ensure that Helm is deploying to the EKS cluster by associating the k8s provider.
}, { provider });

// If you want to access the Helm Chart resources after deployment then you can export them.
export const chartResources = helmChart.resources;
```

Explanation:

- First, we create an EKS cluster using `eks.Cluster`. The name "pulumi-eks-cluster" is the logical name Pulumi will use to refer to the cluster resources. This class abstracts away much of the setup required, but you can configure the number of instances, instance types, and other cluster settings by passing parameters to the `eks.Cluster` constructor. The `storageClasses` parameter specifies the default storage class. The `deployDashboard` parameter configures whether to deploy the Kubernetes dashboard, which we're opting out of in this case.
  
- We then export the `kubeconfig`, which will be used to interact with the cluster. The kubeconfig output will contain the necessary cluster connection information when Pulumi has finished creating the cluster.

- Next, we create a Kubernetes provider linked to the new EKS cluster with the exported `kubeconfig`. We need this because the Helm chart is to be deployed on Kubernetes, so we must tell Pulumi which Kubernetes cluster to work with and how to access it.

- We deploy the Helm chart using `k8s.helm.v3.Chart`. The `repo` and `chart` arguments in the constructor would need to be updated with the Helm repository where the `teleport-operator` chart is hosted. The `values` parameter allows you to provide any overrides to the default configurations of the `teleport-operator` chart.

- Optionally, you can export the `chartResources` which represent the Kubernetes resources created as part of the Helm chart deployment.

Remember to replace `"stable"` and `"teleport-operator"` with the appropriate Helm repository and chart names for `teleport-operator`. This information can usually be found in the documentation for the chart you want to deploy.

Run the Pulumi program with the following commands:

```bash
pulumi up # preview and deploy changes
```

When you run this command, Pulumi will provision the necessary AWS resources, create the EKS cluster, and deploy the Helm chart.

If there are any specific configurations needed for the `teleport-operator` Helm chart, such as setting custom values or configuring RBAC, those should be included in the `values` parameter or additional Pulumi resources as needed. Please consult the Helm chart's documentation for those details.