1. Deploy the wbaas-backup helm chart on Rancher


    To deploy a Helm chart on a Rancher-managed Kubernetes cluster using Pulumi, you will need to use the Pulumi Rancher2 provider, which allows for the management of Rancher resources including Helm charts.

    To accomplish this in TypeScript, you will follow these general steps:

    1. Create a Pulumi project: Set up a new Pulumi project and install the required dependencies.
    2. Configure Rancher2 provider: Include the necessary Rancher2 provider configuration so Pulumi can authenticate with your Rancher instance.
    3. Use the rancher2.App resource: Provision the wbaas-backup Helm chart.

    Below is the detailed code, which demonstrates how to deploy a Helm chart to a Rancher cluster using Pulumi:

    import * as rancher2 from "@pulumi/rancher2"; // Note: The following values such as `clusterId`, `catalog name`, `catalog URL`, and `projectId` // must be changed to match the actual IDs, names, and URLs in your Rancher environment. // Create a catalog to add the Helm chart repository in Rancher const catalog = new rancher2.CatalogV2("wbaas-backup-catalog", { url: "https://charts.example.com/", // Replace with the actual Helm chart repository URL clusterId: "c-abcde", // Replace with the actual cluster ID // Other configurations like `gitBranch` and namespace settings can be added as needed. }); // Deploy the Helm chart from the catalog const wbaasBackupApp = new rancher2.AppV2("wbaas-backup", { // Replace `projectId` with the actual Rancher project ID where the app should be deployed namespace: "default", projectId: "c-abcde:p-abcde", repoName: catalog.name, chartName: "wbaas-backup", // The name of the chart in your repository chartVersion: "1.0.0", // Specify the version of the chart you want to deploy values: {}, // Specify any custom values for your Helm chart (as a YAML string or an object) }); // Export the App's name export const appName = wbaasBackupApp.name;


    • First, you create a catalog that points to the Helm chart's repository. The url should be the exact location of your Helm chart repository.
    • By creating an instance of rancher2.AppV2, you deploy the Helm chart to your Rancher-managed Kubernetes cluster.
    • The projectId passed to rancher2.AppV2 is a concatenation of the cluster id (c-abcde) and the project id (p-abcde) separated by a colon. This is typically found in your Rancher dashboard.
    • The repoName property should match the name you gave to the rancher2.CatalogV2.
    • The values property of rancher2.AppV2 is used to pass custom values to the Helm chart. It can be an empty object if no custom values are needed, or it can contain the configuration specific to your deployment needs.
    • After deploying this code with pulumi up, the Helm chart specified would be deployed to the given Rancher Kubernetes project.

    Remember to replace placeholder values with actual values from your Rancher installation. You must have appropriate permissions to deploy applications to the Rancher cluster. Additionally, your Pulumi stack must be correctly configured with access to the Rancher2 provider.

    Please ensure that you have the Pulumi CLI installed and configure it to interact with your Rancher environment. For Rancher-specific authentication settings, refer to the Pulumi documentation for the Rancher2 provider.