Deploy the uow-cca-groupt-hc helm chart on Rancher

Question

Pulumi · Accepted Answer

To deploy a Helm chart on Rancher using Pulumi, you'll first need to set up your Rancher provider and then use Rancher-specific resources to manage your Kubernetes cluster and applications. In this case, we'll create a Helm chart resource on a Rancher-managed Kubernetes cluster.

Pulumi's rancher2 package provides the necessary resources for managing Rancher. Assuming you have Rancher installed and configured with a Kubernetes cluster, and you have the necessary credentials on your local machine to interact with Rancher's API, here's what you'll need to do:

Set up the Rancher provider.
Define the Kubernetes cluster managed by Rancher where the Helm chart will be deployed.
Deploy the Helm chart using the rancher2.CatalogV2 and rancher2.AppV2 resources to add the Helm repository and deploy the chart, respectively.

Below is a Pulumi TypeScript program that outlines these steps to deploy the uow-cca-groupt-hc Helm chart on a Rancher-managed Kubernetes cluster. Please make sure to replace placeholders such as "<RANCHER_API_URL>", "<RANCHER_ACCESS_KEY>", "<RANCHER_SECRET_KEY>", "<CLUSTER_ID>", and the Helm chart details with your actual information.

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

// Instantiate Rancher provider
const rancherProvider = new rancher2.Provider("rancher", {
    api_url: "<RANCHER_API_URL>",
    accessKey: "<RANCHER_ACCESS_KEY>",
    secretKey: "<RANCHER_SECRET_KEY>",
});

// You need to reference an existing cluster managed by Rancher here
const cluster = new rancher2.Cluster("cluster", {
    // Properties for your specific cluster,
    // Refer to the Pulumi documentation for the Cluster resource:
    // https://www.pulumi.com/registry/packages/rancher2/api-docs/cluster/
    // This is where you would specify the cluster you are targeting.
    name: "<CLUSTER_NAME>",
    // ... other necessary cluster configurations
});

// Add the Helm repository as a Catalog in Rancher
const catalog = new rancher2.CatalogV2("helmRepo", {
    clusterId: cluster.id,
    name: "<HELM_CHART_REPO_NAME>",
    url: "<HELM_CHART_REPO_URL>", // URL to the repository where the Helm chart is located
    // ... other necessary catalog configurations
});

// Deploy the Helm chart using the App resource in Rancher
const app = new rancher2.AppV2("HelmApp", {
    clusterId: cluster.id,
    namespace: "<TARGET_NAMESPACE>", // Namespace where the Helm chart should be deployed
    repoName: catalog.name,
    chartName: "uow-cca-groupt-hc", // The name of the chart you want to deploy
    chartVersion: "<CHART_VERSION>", // Specific version of the chart, if required
    // valuesYaml represents Helm's values.yaml file content in string format for chart customizations
    valuesYaml: `
    # Override the default values in your values.yaml
    # replicaCount: 2
    # image:
    #   repository: nginx
    #   tag: stable
    # ... additional custom values
    `,
    // ... other necessary app configurations
}, {dependsOn: [catalog]}); // Ensures the catalog is created before the app

// Export any useful information, typically URLs to access your application
export const appUrl = pulumi.interpolate`http://<APPLICATION_ENDPOINT>`;

In this program:

We instantiate the Rancher provider by supplying the API URL and credentials needed for Pulumi to communicate with Rancher.
We assume a Rancher Cluster resource already exists or reference a pre-existing cluster. If you need to create a new cluster, you will need additional configuration specific to the cloud provider you are using.
The CatalogV2 resource represents a Helm chart repository where we define the URL location of the Helm repository that contains the uow-cca-groupt-hc Helm chart.
The AppV2 resource represents the Helm chart deployment within Rancher. We specify the chart to deploy as well as any custom values needed for the deployment using the valuesYaml property.

Remember to update all placeholders with your specific configurations. The above is a starting template and may need adjustments depending on your Rancher setup, the specifics of the Helm chart you're deploying, and the requirements of your Kubernetes cluster managed by Rancher.