Deploy the ibm-mariadb-dev helm chart on Rancher

Question

Pulumi · Accepted Answer

### Deploying an IBM MariaDB Helm Chart on Rancher with Pulumi

To deploy an IBM MariaDB development Helm Chart on a Rancher managed Kubernetes cluster, you'll want to set up the appropriate resources in Rancher and then leverage Pulumi to orchestrate deployment.

The first step in this process is to ensure that you have a Kubernetes cluster managed by Rancher. With Pulumi, you can take advantage of the `rancher2` provider to interact with Rancher from your code. One of the key resources you will interact with using Pulumi is `CatalogV2`. This resource allows you to create a global catalog pointing to the helm repository containing your desired chart.

Here's a Pulumi program using TypeScript to deploy a helm chart (in this case, `ibm-mariadb-dev`) to a Rancher managed Kubernetes cluster. This sample assumes that you've already set up Rancher and have a cluster ready for deployment.

Before you start with the TypeScript code, make sure to install the necessary dependencies using npm:

```bash
npm install @pulumi/rancher2
```

Below is the TypeScript program. Please enter this program into a file, usually named `index.ts` in your Pulumi project directory:

```typescript
import * as rancher2 from "@pulumi/rancher2";

// Assuming you've already logged in to Rancher and have the required permissions,
// provide the name of the Kubernetes cluster managed by Rancher where you want to
// deploy the MariaDB helm chart.
const clusterName = "your-rancher-cluster-name";

// Create a new catalog within Rancher that points to the Helm repository
// containing the IBM MariaDB development chart. 
// Replace 'YOUR-CATALOG-URL' with the actual URL to the helm chart repository.
const catalog = new rancher2.CatalogV2("ibm-mariadb-dev-catalog", {
    clusterId: clusterName,
    url: "YOUR-CATALOG-URL", // e.g., "https://charts.bitnami.com/bitnami" if using a Bitnami chart.
    gitBranch: "main",
});

// Deploy the ibm-mariadb-dev helm chart using rancher2.AppV2 resource.
// You'll need to provide the name of your chart, version, and any necessary
// values that the chart requires. The values here ('namespace', 'chart', 'repoName', etc.)
// should be replaced with the actual values corresponding to the target deployment.
const mariadbApp = new rancher2.AppV2("ibm-mariadb-dev-app", {
    clusterId: clusterName,
    chartName: "ibm-mariadb-dev",
    namespace: "default",                // You can specify a custom namespace if needed.
    projectName: catalog.status.id,      // projectId is derived from the CatalogV2 resource created earlier.
    repoName: catalog.metadata.name,     // The name of the helm repository from the catalog resource.
    values: {                            // Populates the 'values.yaml' for the helm chart.
        // Replace these with appropriate values of your ibm-mariadb-dev chart.
        "mariadb": {
            "user": "admin",
            "password": "adminpassword",
            // Add additional configuration parameters as needed.
        },
    },
    version: "x.x.x",                    // Specify the version of your chart.
});

// Export the name of the deployed app.
export const mariadbAppName = mariadbApp.metadata.name;
```

In the above program, replace `'your-rancher-cluster-name'` with the actual name of your Rancher-managed Kubernetes cluster and update the placeholder `'YOUR-CATALOG-URL'` with the URL to the IBM MariaDB Helm repository. Also, set the chart version to the version you want to install and adjust the values section to configure MariaDB as needed.

To execute the Pulumi program:
1. Set up your Rancher access configurations and credentials properly.
2. Run `pulumi up` in the directory containing your Pulumi TypeScript file.

This process will hook into Pulumi's deployment engine to create a catalog and then deploy the IBM MariaDB development helm chart onto your Kubernetes cluster managed by Rancher. The specific configuration details such as user credentials for MariaDB should be securely handled and may come from a secure store or Pulumi's configuration system in a real-world scenario.

Keep in mind that when managing infrastructure as code, it's vital to manage sensitive information, such as passwords or access tokens securely. Pulumi allows you to manage secrets in a variety of ways including encryption and secret stores, which are beyond the scope of this example but can be read about in [Pulumi's Secrets Management documentation](https://www.pulumi.com/docs/intro/concepts/secrets/).

Note: The actual MariaDB helm repository URL should be known prior to deployment, along with the necessary configuration values for the helm chart which are typically available in the chart's documentation.