1. Deploy the kamaji-console helm chart on AWS EKS


    To deploy the kamaji-console Helm chart on AWS EKS, you will need to create an EKS Cluster, configure your Kubernetes provider to interact with the cluster, and then deploy the Helm chart to it.

    Let's go through the steps:

    1. Create an EKS Cluster: Utilize aws.eks.Cluster to create an EKS cluster. You'll need to define resources like VPC and subnets outside of this program since deploying a full VPC is beyond the scope of this example. For simplicity, this example assumes you already have a VPC and subnets where you want to deploy your EKS cluster.

    2. Configure Kubernetes Provider: Once the EKS cluster is created, you will have to configure the Kubernetes provider to target your newly created EKS cluster.

    3. Deploy Helm Chart: With everything set up, you can now deploy the kamaji-console Helm chart using kubernetes.helm.v3.Chart.

    Here's how you would write the Pulumi program in TypeScript:

    import * as pulumi from "@pulumi/pulumi"; import * as aws from "@pulumi/aws"; import * as eks from "@pulumi/eks"; import * as k8s from "@pulumi/kubernetes"; // Step 1: Create the EKS cluster const vpcId = "vpc-12345678"; // Replace with your VPC ID const subnetIds = ["subnet-12345678", "subnet-87654321"]; // Replace with your Subnet IDs const role = new aws.iam.Role("eksRole", { assumeRolePolicy: JSON.stringify({ Version: "2012-10-17", Statement: [ { Effect: "Allow", Principal: { Service: "eks.amazonaws.com" }, Action: "sts:AssumeRole" } ] }) }); const cluster = new eks.Cluster("eksCluster", { vpcId: vpcId, subnetIds: subnetIds, instanceType: "t2.medium", desiredCapacity: 2, minSize: 1, maxSize: 2, storageClasses: "gp2", deployDashboard: false, roleMappings: [{ // Map the IAM role for Kubernetes admin (cluster creator) to `system:masters` in Kubernetes roleArn: role.arn, groups: ["system:masters"], username: "admin", }], }); // Export the cluster's kubeconfig. export const kubeconfig = cluster.kubeconfig; // Step 2: Configure Kubernetes provider const provider = new k8s.Provider("k8sProvider", { kubeconfig: kubeconfig, }); // Step 3: Deploy the kamaji-console Helm chart const kamajiConsoleChart = new k8s.helm.v3.Chart("kamaji-console", { chart: "kamaji-console", // Replace "<YOUR-REPO-NAME>" with the name of your Helm chart repository repo: "<YOUR-REPO-NAME>", namespace: "default", }, { provider }); // Export the Helm chart deployment status export const kamajiConsoleDeploymentStatus = kamajiConsoleChart.status;

    In this program:

    • We create an IAM role for the EKS cluster which allows the cluster to make calls to AWS services on your behalf.
    • The cluster detail including instance type, VPC ID, and subnet IDs are configured. These instances will form the nodes of your EKS cluster.
    • A Kubernetes provider is then set up with the kubeconfig of the EKS cluster. This provider will allow us to deploy Kubernetes resources to our cluster.
    • Finally, the kamaji-console Helm chart is deployed to the default namespace of your EKS cluster using the k8s provider. You need to specify the repo which is the name of the repository where your Helm chart resides.

    Please replace placeholder strings like vpc-12345678, subnet-12345678, and <YOUR-REPO-NAME> with actual values from your AWS environment and Helm chart repository.

    Remember that EKS clusters can incur costs in your AWS account, and deploying Kubernetes resources can further add to those costs depending on resources requested by the Helm chart, so keep an eye on your resources and clean up as necessary.