Deploy the phppgadmin helm chart on Rancher

Question

Pulumi · Accepted Answer

Deploying a Helm chart on Rancher involves several steps. First, you need to set up Pulumi with the Rancher 2 provider, which allows you to interact with your Rancher instance programmatically. Then you'll need to add a catalog (if it's not already present) that includes the phppgadmin chart. Once the catalog is in place, you can deploy the Helm chart to a specific project within a Rancher cluster.

Below is a TypeScript program using Pulumi to deploy the phppgadmin Helm chart on Rancher:

Set up the Rancher 2 provider: This provider will be used to interact with your Rancher instance.
Create a Catalog: This creates a new or selects an existing catalog where the Helm chart is located.
Deploy a Helm Chart: This will deploy the phppgadmin Helm chart from the specified catalog into a Rancher project.

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

// Set the Rancher API URL and access credentials. Ensure these values are set correctly to authenticate with your Rancher cluster.
const rancherApiUrl = "https://rancher.mycompany.com/v3";
const rancherAccessToken = "<YOUR_RANCHER_ACCESS_TOKEN>";

// Initialize the Rancher provider with the given API URL and access token
const rancherProvider = new rancher2.Provider("rancher", {
  apiUrl: rancherApiUrl,
  accessKey: "<YOUR_RANCHER_ACCESS_KEY>",
  secretKey: "<YOUR_RANCHER_SECRET_KEY>",
});

// Create or use existing Catalog - Helm repository in Rancher
// Replace the `url` with the actual Helm repository URL that contains the `phppgadmin` chart.
const catalog = new rancher2.CatalogV2("phppgadmin-catalog", {
  url: "https://charts.mycompany.com/", // The URL for the Helm repo
  clusterId: "<YOUR_CLUSTER_ID>", // The ID of the cluster where you want to deploy the Helm chart
}, { provider: rancherProvider });

// Deploy the `phppgadmin` Helm chart into a project within Rancher
// To find the projectId, navigate to the project within Rancher and copy the ID from the URL.
const helmRelease = new k8s.helm.v3.Release("phppgadmin", {
  chart: "phppgadmin", // The name of the chart you want to deploy
  version: "1.0.0", // Specify the chart version if needed
  repositoryOpts: {
    repo: catalog.url, // This should match the repository URL you used in catalog
  },
  values: {
    // Insert any necessary values for the 'phppgadmin' Helm chart
  },
  namespace: "default", // Kubernetes namespace in the project to deploy to
  project: "<YOUR_PROJECT_ID>", // The Rancher project ID where you want to deploy the app
}, { provider: rancherProvider });

// Export the name of the release and the URL used
export const releaseName = helmRelease.metadata.apply(m => m.name);

In this program:

We import the necessary Pulumi packages for the Rancher2 provider and Kubernetes.
We set up Rancher authentication parameters, which you need to replace with your own Rancher instance's URL and access token.
The Rancher2.CatalogV2 resource specifies where Pulumi can find the Helm chart for phppgadmin, which needs to be substituted with the actual repository URL.
The Release resource is from the @pulumi/kubernetes package, which actually deploys the Helm chart into the Rancher project used.

Please replace the placeholders with the actual values for your setup, like <YOUR_RANCHER_ACCESS_TOKEN>, <YOUR_RANCHER_ACCESS_KEY>, <YOUR_RANCHER_SECRET_KEY>, <YOUR_CLUSTER_ID>, and <YOUR_PROJECT_ID>.

Keep in mind that the above program assumes that you have the proper permissions and access set up within your Rancher and Kubernetes environments, and that you have Pulumi set up and configured on your machine.