Deploy the wordpress-apache helm chart on AWS EKS

Question

Pulumi · Accepted Answer

To deploy the `wordpress-apache` Helm chart on AWS EKS using Pulumi, you will first need to set up an Amazon EKS cluster, if you don't have one already. Then, you will use the Pulumi Kubernetes provider to install the Helm chart onto your EKS cluster.

Below is a detailed explanation and Pulumi TypeScript program to accomplish this. The essential steps in the program are as follows:

1. Create an EKS cluster using the `@pulumi/eks` package.
2. Deploy the `wordpress-apache` Helm chart onto the EKS cluster using the `@pulumi/kubernetes` package.

Let's start with the TypeScript program to achieve this setup:

```typescript
import * as pulumi from '@pulumi/pulumi';
import * as eks from '@pulumi/eks'; // High-level EKS cluster creation.
import * as k8s from '@pulumi/kubernetes'; // Kubernetes provider to interact with the EKS cluster.

// Create an EKS cluster.
const cluster = new eks.Cluster('myEksCluster', {
    version: '1.21', // Specify the EKS cluster version (Make sure the version is supported by AWS and by wordpress-apache Helm chart)
    instanceType: 't2.medium', // Specify the instance type for the worker nodes (Adjust based on desired performance and cost considerations)
    desiredCapacity: 2, // Adjust the desired number of worker nodes in the cluster
    minSize: 1, // Minimum number of worker nodes
    maxSize: 3, // Maximum number of worker nodes
    // Other configurations like VPC, IAM roles, etc., can also be specified.
});

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

// Create a Kubernetes provider instance with the cluster's kubeconfig.
const provider = new k8s.Provider('eksProvider', {
    kubeconfig: cluster.kubeconfig,
});

// Deploy wordpress-apache Helm chart using the Kubernetes provider.
const wordpressApacheChart = new k8s.helm.v3.Chart('wordpress-apache', {
    chart: 'wordpress',
    version: '7.6.7', // The version of the wordpress-apache helm chart (Check the chart repository for the latest version)
    namespace: 'default', // Kubernetes namespace to deploy the Helm chart
    fetchOpts: {
        repo: 'https://charts.bitnami.com/bitnami' // Helm chart repository URL
    },
}, { provider }); // Ensure that this Helm chart is installed using our EKS cluster's provider.

// Export the WordPress service endpoint to access the deployment.
export const wordpressEndpoint = wordpressApacheChart
    .getResourceProperty("v1/Service", "default", "wordpress-apache-wordpress", "status")
    .apply(status => status.loadBalancer.ingress[0].hostname);
```

Here's an explanation of what each part does:

- The `eks.Cluster` class from `@pulumi/eks` is used to provision a new EKS cluster in your AWS account. This cluster will be composed of the necessary AWS resources like EC2 instances (as EKS worker nodes), an EKS cluster, security groups, and IAM roles.
- The `k8s.Provider` class from `@pulumi/kubernetes` represents the Kubernetes provider that will interact with the just-created EKS cluster. It's configured to use the `kubeconfig` generated by the EKS cluster so that it has the necessary access permissions.
- The `k8s.helm.v3.Chart` class is used to deploy a Helm chart, in this case, the `wordpress` chart from the Bitnami repository. You can replace `'wordpress'` and `'7.6.7'` with the chart and version for `wordpress-apache` if it's different. The `fetchOpts` attribute specifies where the Helm chart can be found.
- The `wordpressEndpoint` is an exported output that will give you the load balancer endpoint once Pulumi has finished deploying the chart. This would be the URL you use to access your WordPress installation.

Once you have this code, save it as `index.ts` and then run `pulumi up` to deploy your infrastructure.

Before running `pulumi up`, make sure you've done the following:
- Install Pulumi CLI and set up the AWS provider by following the instructions on the [Pulumi installation page](https://www.pulumi.com/docs/get-started/aws/install-pulumi/).
- Configure your AWS credentials using the [AWS Configuration guide](https://www.pulumi.com/registry/packages/aws/installation-configuration/).
- Have `kubectl` installed and configured, if you want to interact with your EKS cluster outside of Pulumi.

This program will create an Amazon EKS cluster and deploy the `wordpress-apache` Helm chart. Once you finish, the endpoint for your WordPress installation will be part of Pulumi's stack output.