Deploy the my-bloody-jenkins helm chart on AWS EKS

Question

Pulumi · Accepted Answer

To deploy the `my-bloody-jenkins` Helm chart on AWS EKS using Pulumi, you'll need to:

1. Create an EKS cluster using the `eks.Cluster` resource from the `eks` package.
2. Deploy the Jenkins chart to the EKS cluster with the `kubernetes.helm.v3.Chart` resource from the `kubernetes` package.

Let's start by setting up an EKS cluster. We'll need to define a VPC (or use an existing one), specify the subnets, and create an IAM role for the cluster:

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

// Create a VPC for our cluster.
const vpc = new awsx.ec2.Vpc("my-vpc", { numberOfAvailabilityZones: 2 });

// Create an EKS cluster with the default configuration.
const cluster = new eks.Cluster("my-cluster", {
    vpcId: vpc.id, // Use the VPC we defined earlier
    subnetIds: vpc.publicSubnetIds, // Use the VPC's public subnets
    instanceType: "t2.medium", // The EC2 instance type for the worker nodes
    desiredCapacity: 2, // The desired quantity of worker nodes
    minSize: 1, // Minimum number of worker nodes
    maxSize: 3, // Maximum number of worker nodes
    storageClasses: "gp2", // The default storage class for EKS
    deployDashboard: false, // Disable EKS dashboard for security purposes
});

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

The above program sets up a new EKS cluster. I have not specified an existing VPC and subnets; this program will create them for you. Adjust the `instanceType` and capacity settings according to the needs of the Jenkins deployment.

Next, we'll deploy the `my-bloody-jenkins` Helm chart to the EKS cluster using the `kubernetes.helm.v3.Chart` resource:

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

// Deploy the 'my-bloody-jenkins' Helm chart using the Kubernetes provider.
const jenkinsChart = new k8s.helm.v3.Chart("my-bloody-jenkins", {
    chart: "my-bloody-jenkins",
    fetchOpts: { repo: "https://example.com/my/helm/repo" }, // Replace with the actual Helm repo URL
    // You can specify additional chart values here, for instance:
    // values: {
    //   persistence: {
    //     storageClass: "gp2",
    //     size: "10Gi"
    //   },
    //   // ...other values
    // },
}, { provider: k8sProvider });

// Export the Jenkins server URL.
export const jenkinsUrl = pulumi.interpolate`http://${cluster.endpoint}/jenkins`;
```

Please replace `https://example.com/my/helm/repo` with the actual URL of the repository containing the `my-bloody-jenkins` chart.

The `my-bloody-jenkins` Helm chart should now be deployed to your EKS cluster. The Jenkins server URL is exported and can be used to access your Jenkins server once it's set up and all resources are properly initialized.

Remember that provisioning a Kubernetes cluster and deploying a Helm chart can take several minutes. After running `pulumi up`, you can watch the progress and see the details of the resources being created or updated.

For more information on using AWS EKS with Pulumi, you can refer to the documentation:
- [`eks.Cluster`](https://www.pulumi.com/registry/packages/eks/api-docs/cluster/)
- [`kubernetes.helm.v3.Chart`](https://www.pulumi.com/registry/packages/kubernetes/api-docs/helm.sh/v3/chart/)

Please ensure that any sensitive data such as AWS credentials are securely handled and not hard-coded into your Pulumi program. Use Pulumi configuration settings or environment variables where appropriate.