1. Deploy the interbtc-parachain helm chart on Rancher


    Deploying a Helm chart on Rancher using Pulumi involves several steps. You'll need to:

    1. Set up Rancher and get access to the Kubernetes cluster where you want to deploy the Helm chart.
    2. Install the Pulumi CLI and the necessary plugins.
    3. Write a Pulumi program to deploy the Helm chart.

    Below, I'm going to provide you with a TypeScript program that uses the Rancher2 Pulumi provider to deploy the interbtc-parachain Helm chart into a Kubernetes cluster managed by Rancher. This guide assumes that you've already set up Rancher and have access credentials to the cluster.

    Step by Step Pulumi TypeScript Program

    First, install the necessary Pulumi packages by running the following commands:

    pulumi plugin install resource rancher2 5.1.1 npm install @pulumi/pulumi @pulumi/kubernetes @pulumi/rancher2

    Next, you'll write a Pulumi program to deploy the Helm chart. In this example, we're using Pulumi's Rancher2 provider and Kubernetes provider.

    import * as pulumi from "@pulumi/pulumi"; import * as k8s from "@pulumi/kubernetes"; import * as rancher2 from "@pulumi/rancher2"; const config = new pulumi.Config(); const rancherApiUrl = config.require("rancherApiUrl"); const rancherAccessToken = config.requireSecret("rancherAccessToken"); const clusterId = config.require("clusterId"); const interbtcNamespace = "interbtc"; // Configure the Rancher2 provider with the API URL and the access token. const rancherProvider = new rancher2.Provider("rancherProvider", { apiUrl: rancherApiUrl, tokenKey: rancherAccessToken, }); // Get the cluster info from Rancher. const cluster = rancher2.getCluster({ id: clusterId, }, { provider: rancherProvider }); // Instantiate a Kubernetes provider to handle deployments within the Rancher cluster. const k8sProvider = new k8s.Provider("k8sProvider", { kubeconfig: cluster.kubeConfig, }); // Create a Kubernetes namespace for the interbtc-parachain Helm chart. const interbtcNamespaceObj = new k8s.core.v1.Namespace("interbtc-ns", { metadata: { // You can set additional labels and annotations if needed name: interbtcNamespace, }, }, { provider: k8sProvider }); // Deploy the interbtc-parachain Helm chart within the namespace. const interbtcHelmChart = new k8s.helm.v3.Chart("interbtc-parachain", { chart: "interbtc-parachain", version: "x.y.z", // Replace with the specific version you want to deploy fetchOpts: { repo: "http://charts.interlay.io/", // Replace with the Helm chart's repository URL }, namespace: interbtcNamespaceObj.metadata.name, // Include necessary values for the Helm chart values: { // Define any values required for the Helm chart deployment }, }, { provider: k8sProvider }); // Export the Helm chart's service endpoint. export const interbtcEndpoint = interbtcHelmChart.getResourceProperty('v1/Service', 'interbtc-parachain', 'status') .apply(status => status.loadBalancer.ingress[0].ip || status.loadBalancer.ingress[0].hostname);


    Here's what each section in the code is doing:

    • Imports: We import Pulumi's core library, Kubernetes library, and the Rancher2 library to interact with such resources.
    • Configuration: Configuration parameters such as Rancher API URL, access token, and cluster ID are required. These would typically be set using Pulumi config, but for the purpose of this example, you need to replace them with your actual values or manage them securely as part of your Pulumi project configuration.
    • Rancher Setup: We set up the Rancher provider using the Rancher API URL and access token.
    • Cluster Information: The program retrieves the cluster information from Rancher. This information is used to configure the Kubernetes provider.
    • Kubernetes Provider: This provider will interact with the Kubernetes API of the cluster managed by Rancher and is set up with the cluster’s kubeconfig.
    • Namespace: We create a Kubernetes namespace dedicated to the interbtc-parachain deployment.
    • Helm Chart: This is the actual deployment of the Helm chart. You have to specify the chart name, version, and repository URL where the Helm chart is located. You also define the namespace to which the chart should be deployed and any additional values required by the Helm chart.
    • Endpoint Export: Finally, the service created by the Helm chart is extracted, and its endpoint is exported, so you can access it.

    This Pulumi program can be used as the basis for deploying the interbtc-parachain Helm chart to your Rancher-managed Kubernetes cluster. Remember to replace placeholders with actual values where appropriate and supply any specific values that might be needed by the Helm chart to customize the deployment.