1. Deploy the http-headers helm chart on AWS EKS


    Deploying an HTTP Headers Helm chart on AWS Elastic Kubernetes Service (EKS) involves several steps. We'll start by establishing an EKS cluster, and then we'll deploy the Helm chart onto that cluster. I'll guide you through this process using Pulumi in TypeScript.


    Before diving into the code, ensure that you have the following:

    • An AWS account with appropriate permissions to create EKS clusters and other related resources.
    • kubectl command-line tool installed, to interact with the Kubernetes cluster.
    • Helm command-line tool installed, to deploy the Helm chart.
    • Pulumi CLI installed and configured with AWS credentials.


    1. Set up an EKS Cluster: Begin by creating a new EKS cluster using the eks.Cluster Pulumi resource.
    2. Deploy a Helm Chart: Once your cluster is ready, use the kubernetes.helm.v3.Chart resource to deploy your Helm chart to the EKS cluster.

    Pulumi Program - TypeScript

    Here's the Pulumi program which accomplishes this:

    import * as pulumi from "@pulumi/pulumi"; import * as aws from "@pulumi/aws"; import * as eks from "@pulumi/eks"; import * as k8s from "@pulumi/kubernetes"; // Create an EKS cluster. const cluster = new eks.Cluster("my-cluster", { desiredCapacity: 2, minSize: 1, maxSize: 3, instanceType: "t2.medium", }); // Export the cluster's kubeconfig. export const kubeconfig = cluster.kubeconfig; // Deploy the http-headers Helm chart into the EKS cluster const httpHeadersChart = new k8s.helm.v3.Chart("http-headers", { chart: "http-headers", version: "0.1.0", // Specify the chart version you want to deploy fetchOpts: { repo: "http://charts.example.com/", // Replace with the URL to the Helm repository }, }, { provider: new k8s.Provider("k8s-provider", { kubeconfig: cluster.kubeconfig }) }); // Expose the services and other resources created export const httpHeadersChartResources = httpHeadersChart.getResource("v1/Service", "http-headers-http-headers");


    1. EKS Cluster Creation

      • The eks.Cluster resource creates a new EKS cluster named "my-cluster". We've specified the desired, minimum, and maximum number of worker nodes, as well as the instance type that they should use.
    2. Export of Kubeconfig

      • kubeconfig is exported so that you can interact with your Kubernetes cluster using kubectl from your local machine.
    3. Helm Chart Deployment

      • The k8s.helm.v3.Chart resource is responsible for deploying the Helm chart to your EKS cluster. You need to specify the chart name, chart version, and the URL to the Helm repository where the chart can be found.
      • A k8s.Provider is instantiated with the kubeconfig from the EKS cluster to ensure that the Helm chart is deployed onto the newly created EKS cluster, not some other cluster you might have configured by default.

    Next Steps:

    After this code is deployed with pulumi up, the HTTP Headers Helm chart will be running in your EKS cluster. To interact with the services, you can retrieve the service endpoints by inspecting the outputs with pulumi stack output.

    If you want to access the applications on your EKS cluster, you will need to use kubectl to set up the necessary port-forwarding or obtain the external IP if the service type is LoadBalancer.

    I hope this provides you with a clear understanding of deploying Helm charts on AWS EKS using Pulumi!