Deploy the gitops-operator helm chart on Oracle Kubernetes Engine (OKE)

Question

Pulumi · Accepted Answer

To deploy the GitOps operator Helm chart on Oracle Kubernetes Engine (OKE), you can use Pulumi's modern infrastructure as code approach. Below is a step-by-step guide on how to accomplish this, followed by the complete TypeScript program.

Step-by-Step Explanation:

Set up your Oracle Kubernetes Engine (OKE): Before deploying any Helm charts, you must have an OKE cluster running. You can create and configure the cluster using Pulumi’s oci.ContainerEngine.Cluster resource.
Install Helm and the GitOps Operator Chart: The kubernetes.helm.v3.Chart resource is an abstraction to deploy charts, a collection of pre-configured Kubernetes resources.
Configure the Kubernetes Provider: You need to configure Pulumi to communicate with your Kubernetes cluster. We’ll use the kubeconfig output from the OKE cluster to set up the Kubernetes provider.
Deploy the GitOps Operator Helm Chart: Provide the chart name, repository, and any necessary values you want to configure for your GitOps Operator Helm chart. By using the kubernetes.helm.v3.Chart resource, Pulumi will handle the Helm release.

Prerequisites:

Make sure you have Pulumi installed and configured with your OCI credentials.
Install Node.js to run the Pulumi program.
Install OCI CLI and set up Kubernetes access using oci ce cluster create-kubeconfig.

Now, let’s write the Pulumi program in TypeScript to deploy the gitops-operator Helm chart on an OKE cluster.

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

// Initialize an OCI provider configuration
const provider = new oci.Provider("oci", {
  // You can specify necessary config values here; otherwise, the OCI SDK looks for OCI configuration in
  // the standard locations (e.g., ~/.oci/config).
});

// Create an OKE cluster. Replace the placeholders with actual values.
const cluster = new oci.ContainerEngine.Cluster("OKECluster", {
  // Specify your compartments, VCNs, and other parameters as required.
  compartmentId: "<compartment-id>",
  // It's recommended to provide other parameters according to your requirements.
});

// Export the cluster's kubeconfig
const kubeconfig = pulumi.all([cluster.id]).apply(([clusterId]) => 
  oci.ContainerEngine.getClusterKubeconfig({ clusterId: clusterId }, { provider: provider })
);

// Use the kubeconfig to create a Kubernetes provider instance
const k8sProvider = new k8s.Provider("okeK8sProvider", {
  kubeconfig: kubeconfig,
});

// Deploy a gitops-operator helm chart on the OKE cluster
const gitopsOperatorChart = new k8s.helm.v3.Chart("gitops-operator", {
  chart: "gitops-operator",
  // Specify the Helm repository containing the gitops-operator chart
  repositoryOpts: {
    repo: "https://charts.your-repository.com",
  },
  // Use `values` to set any custom chart values, for example:
  // values: { key1: "value1", key2: "value2" },
}, { provider: k8sProvider });

// Export the URL for the application (assuming it is exposed via a LoadBalancer service)
const frontend = gitopsOperatorChart.getResource("v1/Service", "gitops-operator-front");
export const frontendUrl = pulumi.all([frontend.spec.apply(spec => spec.clusterIp), frontend.metadata.apply(md => md.name)])
  .apply(([ip, name]) => `http://${ip}:80`);

Explanation of the Program:

We initiate a new OAuth provider for Oracle Cloud (oci.Provider).
A new OKE Cluster is created with the required values. Fill in placeholders like compartment-id with actual values from your OCI setup.
We retrieve the kubeconfig for the created cluster which allows Pulumi to communicate with it.
A Kubernetes provider is created with this kubeconfig.
Then, we define a new Helm chart resource (k8s.helm.v3.Chart) for the GitOps operator, specifying the Helm chart and the repository where it can be found.
At last, we export a frontend URL for ease of access. This assumes that the Helm chart creates a LoadBalancer service to expose the deployment.

Make sure you replace placeholders like <compartment-id> with actual values you want to use in your OCI configuration. Additionally, if you have specific Helm values to configure, replace or augment the values object inside the gitopsOperatorChart variable accordingly.

Remember to execute the program by running pulumi up. This command will provision the OCI resources defined, deploy the Helm chart, and output any exported variables like frontendUrl.