1. Deploy the rabbitmq-observability helm chart on AWS EKS


    To deploy the RabbitMQ Observability Helm Chart on AWS EKS using Pulumi, you will follow a series of steps:

    1. Create an EKS cluster to host your Kubernetes workloads.
    2. Once the cluster is active, configure Pulumi to use the kubeconfig from EKS.
    3. Deploy the RabbitMQ Helm chart using the @pulumi/kubernetes package, which allows deploying Helm charts to a Kubernetes cluster.

    Below is a program written in TypeScript that showcases these steps. The program will:

    • Utilize AWS resources to provision an EKS cluster (using @pulumi/eks).
    • Install the RabbitMQ Observability chart from Helm's stable repository to the cluster.
    import * as eks from "@pulumi/eks"; import * as pulumi from "@pulumi/pulumi"; 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; // Use the generated kubeconfig to connect to the EKS cluster. const provider = new k8s.Provider("k8s-provider", { kubeconfig: cluster.kubeconfig.apply(JSON.stringify), }); // Deploy RabbitMQ Observability Helm chart const rabbitMqChart = new k8s.helm.v3.Chart("rabbitmq-observability", { chart: "rabbitmq", version: "8.22.5", // Specify the version of the RabbitMQ Helm chart namespace: "default", fetchOpts: { repo: "https://charts.bitnami.com/bitnami", // RabbitMQ Helm chart repository }, }, { provider }); // Export the Chart name export const rabbitMqChartName = rabbitMqChart.metadata.apply(m => m.name); // When running this program, Pulumi will invoke the above code and create the EKS cluster and deploy the RabbitMQ Helm chart.


    1. We imported the necessary Pulumi packages (@pulumi/eks for EKS, @pulumi/pulumi for core Pulumi functionality, and @pulumi/kubernetes to interact with Kubernetes).

    2. We created an instance of an EKS cluster using the eks.Cluster class. This keeps the default configuration, but you can customize the node count, node size, and other settings if needed.

    3. We exported the generated kubeconfig, which will be used to manage Kubernetes resources within the EKS cluster.

    4. We instantiated a new k8s.Provider which will use the kubeconfig from the EKS cluster. This will provide the context needed for Pulumi to deploy Kubernetes resources on this specific cluster.

    5. Using the k8s.helm.v3.Chart class, we deployed the RabbitMQ Observability Helm chart to the EKS cluster within the default Kubernetes namespace. Make sure to specify the correct version and repository URL for the Helm chart you wish to deploy – in this case, we're using Bitnami's RabbitMQ chart version 8.22.5.

    6. Finally, we exported the name of the RabbitMQ chart which will be used in the Pulumi stack output.

    Post-Deployment Steps:

    After running the Pulumi program, the infrastructure will be provisioned, and RabbitMQ will be up and running on your EKS cluster. You can interact with the RabbitMQ instance using Kubernetes tools like kubectl or by using the RabbitMQ web interface if it's configured to be exposed with external access.

    Remember to consider the network and security configurations for your RabbitMQ deployment to ensure it's setup according to your requirements, especially if it is accessible over the internet.