Deploy the mariadb-persistent helm chart on AWS EKS

Question

Pulumi · Accepted Answer

Deploying a `mariadb-persistent` Helm chart on an AWS EKS cluster involves several steps. First, you'll need an EKS cluster ready to run your Helm chart. With Pulumi, you can express your infrastructure in code and provision it easily. Below, I'll walk you through creating an EKS cluster and deploying a `mariadb-persistent` Helm chart to that cluster.

1. **Creating the EKS Cluster**: We will use the `eks.Cluster` component from the Pulumi EKS package, which simplifies creating and managing an EKS cluster.

2. **Deploying the Helm Chart**: After setting up the cluster, we will use the `kubernetes.helm.v3.Chart` resource from the Pulumi Kubernetes provider to deploy the `mariadb-persistent` chart.

Here is the Pulumi program that completes the task:

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

// Create an EKS cluster with the default configuration.
const cluster = new eks.Cluster('my-cluster', {});

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

// Create a Kubernetes provider instance that uses our cluster from above.
const k8sProvider = new k8s.Provider('k8s-provider', {
    kubeconfig: cluster.kubeconfig.apply(JSON.stringify),
});

// Deploy mariadb-persistent Helm chart to the EKS cluster
const mariadbChart = new k8s.helm.v3.Chart('mariadb-persistent', {
    chart: 'mariadb',
    version: 'YOUR_DESIRED_CHART_VERSION', // specify the version you want
    fetchOpts: {
        repo: 'https://charts.bitnami.com/bitnami', // assuming using Bitnami's helm repository
    },
    values: {
        // You can specify your custom values for the Helm chart here
        // For example:
        // persistence: {
        //     size: '10Gi',
        // },
        // rootUser: {
        //     password: 'YOUR_PASSWORD',
        // },
        // replication: {
        //     enabled: false,
        // },
        // ...
    },
}, { provider: k8sProvider });

// Export the status of the helm release
export const mariadbStatus = mariadbChart.status;
```

This program starts by importing the necessary Pulumi packages. It then creates an EKS cluster (`my-cluster`) with the default configuration. After the cluster creation, we define a Kubernetes provider to interact with the cluster.

We use the `k8s.helm.v3.Chart` resource to deploy the `mariadb-persistent` Helm chart with the specified version and from the given repo URL. We are assuming that the Helm chart is available from the Bitnami repository, which is a common place to find such charts. The `values:` field in the Chart definition is where you can override default settings with your desired configuration.

The `kubeconfig` and the status of the Helm release are exported, which allows you to interact with your cluster using `kubectl` and verify the status of your MariaDB deployment.

Before applying this program, make sure you have Pulumi and AWS CLI installed and configured with the appropriate credentials.

To apply this Pulumi program:

1. Save the code into a file named `index.ts`.
2. Run `pulumi up` in the directory containing your `index.ts` file. Pulumi will perform the deployment and show you the progress.
3. Once applied, you'll see the exported `kubeconfig` and `mariadbStatus`, which you can use to interact with your EKS cluster and MariaDB deployment respectively.