Deploy the typesense helm chart on Azure Managed Openshift Service

Question

Pulumi · Accepted Answer

To deploy the Typesense Helm chart on an Azure Managed OpenShift Service, you need to perform several steps:

Provision an Azure Managed OpenShift Service (ARO) cluster
Setup Helm in your environment
Deploy the Typesense Helm chart to the ARO cluster

For step 1, you can use the azure-native.redhatopenshift.OpenShiftCluster resource to provision an ARO cluster in your Azure environment. For step 2, you need to have Helm installed in your local/CI environment to interact with Kubernetes. Step 3 involves using the Helm CLI or the Pulumi Kubernetes provider to deploy the Typesense Helm chart.

I will guide you through setting up an ARO cluster using Pulumi and Azure Native Provider (Typescript). You will need to have an Azure account and Pulumi installed on your local machine.

Next, install the required dependencies using npm or yarn:

npm install @pulumi/azure-native @pulumi/kubernetes

or

yarn add @pulumi/azure-native @pulumi/kubernetes

Once you have everything set up, you can write your Pulumi code:

import * as pulumi from "@pulumi/pulumi";
import * as azure_native from "@pulumi/azure-native";
import * as kubernetes from "@pulumi/kubernetes";

// Create an Azure Resource Group if you don't have one already
const resourceGroup = new azure_native.resources.ResourceGroup("resourceGroup", {
    resourceGroupName: "my-aro-resource-group",
    location: "East US", // choose the appropriate Azure region
});

// Deploy Azure Red Hat OpenShift Cluster
const openshiftCluster = new azure_native.redhatopenshift.OpenShiftCluster("openshiftCluster", {
    resourceGroupName: resourceGroup.name,
    resourceName: "myAroCluster", // Name your cluster
    location: resourceGroup.location,
    clusterProfile: {
        domain: "example", // Replace with your domain
        pullSecret: "<pull secret>", // Your Red Hat pull secret
        resourceGroupId: resourceGroup.id,
    },
    masterProfile: {
        vmSize: "Standard_D8s_v3",
    },
    networkProfile: {
        podCidr: "10.0.0.0/16",
        serviceCidr: "10.1.0.0/16",
    },
    workerProfiles: [{
        count: 3,
        vmSize: "Standard_D4s_v3",
        name: "worker", // Name your worker profile
    }],
    apiServerProfile: {
        visibility: "Public",
    },
    ingressProfiles: [{
        name: "default",
        visibility: "Public",
    }],
    servicePrincipalProfile: {
        clientId: "<azure-ad-app-client-id>",
        clientSecret: "<azure-ad-app-client-secret>",
    },
});

// Export the kubeconfig of the ARO cluster to connect with kubectl
export const kubeconfig = openshiftCluster.kubeconfig;

// Setup Helm and deploy the Typesense Helm chart
// Setting up Helm in your environment is a manual step. You need to follow Helm's documentation to do so.
// Once Helm is set up and configured to use the ARO cluster's kubeconfig, you can deploy the Typesense Helm chart with following helm command:
// helm repo add typesense https://dl.typesense.org/beeta-helm
// helm install my-typesense typesense/typesense --values my-values-file.yaml

In the code above, replace the placeholders <pull secret>, <azure-ad-app-client-id>, and <azure-ad-app-client-secret> with your actual credentials. These are necessary to authenticate and provision resources in Azure.

Please note that to keep the code simple, many optional parameters (like tags or detailed networking configuration) were omitted. You might want to add those depending on your specific needs.

After executing the Pulumi program and establishing the ARO cluster, you switch to Helm to deploy the Typesense chart. You must install Helm on your system and use the kubeconfig output from Pulumi to interact with your cluster.

The Helm commands commented out at the end of the program would typically be executed on your command line after the ARO cluster is up and running. They add the Typesense Helm repository and deploy the Typesense Helm chart with your customized values.

Be sure to review the Typesense chart's values file and adjust it according to your requirements before deploying it. This file (my-values-file.yaml) would contain all the configurations specific to Typesense that you want to override or specify.