1. Deploy the argo-cr helm chart on Azure Managed Openshift Service


    To deploy the Argo CD Helm chart on an Azure Managed OpenShift Service using Pulumi, you'll follow these general steps:

    1. Set up an Azure Managed OpenShift cluster: This is the Kubernetes cluster provided by Azure where you'll deploy Argo CD. The resource azure-native.containerservice.OpenShiftManagedCluster is used to create an OpenShift cluster.

    2. Install the Helm chart for Argo CD: Once the cluster is up and running, you can use Pulumi's Helm chart support to deploy Argo CD. The resource kubernetes.helm.v3.Chart can be used for this purpose, where you specify the Helm chart details for Argo CD.

    Below is a TypeScript program that demonstrates how to perform both of these steps using Pulumi. This program assumes you have the Azure and Kubernetes Pulumi providers configured and that you have the necessary permissions to create resources in Azure and deploy to the cluster.

    import * as azure_native from "@pulumi/azure-native"; import * as k8s from "@pulumi/kubernetes"; import * as pulumi from "@pulumi/pulumi"; // Step 1: Create an Azure Managed OpenShift cluster const resourceName = "myOpenShiftCluster"; const resourceGroupName = "myResourceGroup"; // Define the Managed OpenShift cluster const openshiftManagedCluster = new azure_native.containerservice.OpenShiftManagedCluster(resourceName, { // Define the resource group, location, and the cluster properties here resourceGroupName: resourceGroupName, location: pulumi.config.require("location"), // e.g., "East US" // Define other properties like networkProfile, masterPoolProfile, agentPoolProfiles as required }); // Step 2: Install the Argo CD Helm chart on the OpenShift cluster const argoChart = new k8s.helm.v3.Chart("argo-cd", { chart: "argo-cd", version: "4.5.5", // Make sure to specify the correct chart version fetchOpts: { repo: "https://argoproj.github.io/argo-helm", // The Helm repository for Argo CD }, // Values to override in the Helm chart (if any) values: { // Specify the Argo CD settings that you wish to customize // e.g., server: { service: { type: "LoadBalancer" } } }, // Set the namespace where you want to deploy Argo CD namespace: "argocd", }, { provider: openshiftManagedCluster }); // Export the cluster's name and the Argo CD server's public endpoint (if created with type LoadBalancer) export const clusterName = openshiftManagedCluster.name; export const argoServerEndpoint = argoChart.getResourceProperty("v1/Service", "argocd/argocd-server", "status") .apply(status => status.loadBalancer.ingress[0].ip || "not-available");

    Remember to replace placeholder values like the resource group name, location, and any specific configurations according to your requirements.


    • azure-native.containerservice.OpenShiftManagedCluster: This class is used to define and provision an Azure Managed OpenShift cluster. You need to define the configurations like location, resource group, networking, and size of the master and agent pools.

    • k8s.helm.v3.Chart: This is Pulumi's representation of a Helm chart, used for deploying packaged applications to Kubernetes. You specify the chart you want to deploy (argo-cd) from the specified Helm repo (the official Argo project Helm repository in this case).

    • export statements: These Pulumi exports provide outputs after the deployment is complete. The clusterName will give you the name of the OpenShift cluster, and the argoServerEndpoint will render the IP address of the Argo CD server if you chose to expose it with a load balancer.

    After writing this program, you'd use the Pulumi CLI to deploy it by running pulumi up. Ensure you've logged in to your Pulumi account and selected the correct stack that corresponds to the environment you want to deploy to.