Deploy the kube-arangodb helm chart on Azure Managed Openshift Service

Question

Pulumi · Accepted Answer

To deploy the `kube-arangodb` helm chart on an Azure Managed OpenShift Service using Pulumi, we'll break down this process into two main steps:

1. **Create an Azure Managed OpenShift Service Cluster**: We'll use the `azure-native.containerservice.OpenShiftManagedCluster` resource to provision an OpenShift cluster.
2. **Deploy the Helm Chart to the OpenShift Cluster**: Once the cluster is provisioned, we will use the `kubernetes.helm.v3.Chart` resource to deploy the `kube-arangodb` chart to the cluster.

We'll assume that you have `kubectl` configured to communicate with your OpenShift cluster and that you have the appropriate permissions to deploy Helm charts.

Here's a program written in TypeScript which illustrates the entire process:

```typescript
import * as pulumi from '@pulumi/pulumi';
import * as azure_native from '@pulumi/azure-native';
import * as k8s from '@pulumi/kubernetes';

// Create an Azure Resource Group
const resourceGroup = new azure_native.resources.ResourceGroup("myResourceGroup", {
    resourceGroupName: "myResourceGroup",
    location: "eastus", // Choose the appropriate Azure region
});

// Create Azure Managed OpenShift Service Cluster
const openshiftCluster = new azure_native.containerservice.OpenShiftManagedCluster("myOpenShiftCluster", {
    resourceGroupName: resourceGroup.name,
    resourceName: "myOpenShiftCluster",
    location: resourceGroup.location,
    openShiftVersion: "v4.3", // Specify the version of OpenShift
    // Create a network profile for the OpenShift cluster, typically in a separate VNet
    networkProfile: {
        vnetCidr: "10.0.0.0/8",
    },
    // Define the agent pools for the OpenShift cluster
    agentPoolProfiles: [{
        name: "mypool",
        count: 3, // Specify the number of nodes
        vmSize: "Standard_D4s_v3", // Specify the VM size for the nodes
        osType: "Linux",
    }],
    masterPoolProfile: {
        count: 3,
        vmSize: "Standard_D8s_v3", // Specify the VM size for the master nodes
    },
});

// Initialize the Kubernetes provider using the cluster credentials
const k8sProvider = new k8s.Provider("k8sProvider", {
    kubeconfig: openshiftCluster.config.kubeconfig, // Use the kubeconfig output from the OpenShift cluster
});

// Deploy the kube-arangodb Helm chart to the OpenShift cluster
const arangoDbChart = new k8s.helm.v3.Chart("kube-arangodb", {
    chart: "arangodb",
    fetchOpts: { repo: "https://kubernetes-charts.arango.com" }, // Specify the Helm chart repository
    // Additional Helm values can be specified if needed
    values: { /* ... */ },
}, { provider: k8sProvider });

// Export the public cluster endpoint
export const clusterEndpoint = openshiftCluster.openShiftApiServerUrl;

// For more information on the resources used, refer to the following documentation:
// - Azure Managed OpenShift Service Cluster: https://www.pulumi.com/registry/packages/azure-native/api-docs/containerservice/openshiftmanagedcluster/
// - Helm charts on Kubernetes: https://www.pulumi.com/registry/packages/kubernetes/api-docs/helm.sh/v3/chart/
```

In this Pulumi program:

- We create an Azure resource group to house our OpenShift cluster.
- We then create an OpenShift Managed Cluster by providing required details such as resource group name, cluster name, OpenShift version, network profile, and agent/masters pool profiles.
- The `k8s.Provider` is initialized with the `kubeconfig` provided by the cluster, thus allowing Pulumi to communicate with our OpenShift cluster.
- Next, we deploy the `kube-arangodb` Helm chart. Notice that we specify the repository URL where the Helm chart is located.

After running this Pulumi program, the OpenShift cluster will be provisioned, and the `kube-arangodb` Helm chart will be installed onto the cluster. You can then interact with ArangoDB via `kubectl`, using the endpoint details from `clusterEndpoint`.

Remember to replace placeholders like version numbers or VM sizes with values that match your requirements and also ensure to check for the latest versions of the resources and if there are any additional required properties that might have been introduced.