Deploy the zookeeper-helm-chart helm chart on AWS EKS

To deploy the zookeeper-helm-chart Helm chart on AWS EKS with Pulumi, we are going to follow these steps:

1. Set up an EKS cluster using the EKS module, which will serve as the Kubernetes environment for our ZooKeeper deployment.
2. Install the Helm chart for ZooKeeper into the EKS cluster, using Pulumi's ability to manage Helm charts as part of the Pulumi Kubernetes provider.

Before we begin writing the code, make sure you have installed Pulumi and configured your AWS credentials properly. You can install Pulumi from Pulumi's installation guide and set up AWS credentials as explained in AWS setup for Pulumi.

Here is the TypeScript program that accomplishes these steps:

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

// Create an EKS cluster.
const cluster = new eks.Cluster("zookeeper-cluster", {
    desiredCapacity: 2,
    minSize: 1,
    maxSize: 3,
    storageClasses: "gp2",
    deployDashboard: false,
});

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

// Create a Kubernetes provider that uses our EKS cluster.
const k8sProvider = new k8s.Provider("k8s-provider", {
    kubeconfig: cluster.kubeconfig,
});

// Deploy the Helm chart for ZooKeeper.
const zookeeperChart = new k8s.helm.v3.Chart("zookeeper-helm-chart", {
    chart: "zookeeper",
    version: "5.20.2", // Replace with the desired version of the zookeeper chart
    fetchOpts: {
        repo: "https://charts.bitnami.com/bitnami",
    },
}, { provider: k8sProvider });

// Export the ZooKeeper service endpoint.
export const zookeeperEndpoint = zookeeperChart.getResourceProperty("v1/Service", "zookeeper-helm-chart-zookeeper", "status").apply(status => status.loadBalancer.ingress[0].hostname);

Detailed Explanation

EKS Cluster Creation

We start by importing the required Pulumi packages and initiating an EKS cluster using the eks.Cluster class. We define the desired capacity, minimum and maximum size of the cluster to ensure that we have enough resources to run ZooKeeper.

Kubernetes Provider

Next, we define a Kubernetes provider, specifying the kubeconfig from our EKS cluster. This provider is how Pulumi will communicate with our Kubernetes cluster to deploy resources.

Deploying the ZooKeeper Helm Chart

We then deploy the zookeeper Helm chart using Pulumi's helm.v3.Chart resource. We specify the chart name, version, and repository URL.

The provider option passed to the chart resource ensures that the Helm chart is installed on the EKS cluster we created earlier.

Exports

Finally, we export two things:

• The kubeconfig to access our cluster with kubectl or other Kubernetes tools.
• The endpoint of the ZooKeeper service, which is obtained by accessing the load balancer ingress hostname from the deployed service status. This will allow you to connect to the ZooKeeper instance.

With these resources, Pulumi will provision an EKS cluster and deploy ZooKeeper within that cluster using the requested Helm chart. Save this code in a file like index.ts, and run pulumi up to deploy the cluster and the chart to your AWS account.