Deploy the cluster-gitlab-runner helm chart on Oracle Kubernetes Engine (OKE)

Deploying GitLab Runner on Oracle Kubernetes Engine

To deploy the cluster-gitlab-runner Helm chart on the Oracle Kubernetes Engine (OKE) using Pulumi, we'll follow a few steps:

Set up and configure the OCI (Oracle Cloud Infrastructure) provider for Pulumi.
Deploy or use an existing Oracle Kubernetes Engine (OKE) cluster.
Install the GitLab Runner Helm chart onto the OKE cluster.

For this scenario, let's assume you already have an OKE cluster up and running. If not, you'll need to create one using the oci.ContainerEngine.Cluster resource. Once the cluster is ready, you'll use the kubernetes.helm.v3.Chart resource to deploy the GitLab Runner on your cluster.

Now, I'll guide you through writing a Pulumi program in TypeScript to accomplish this task.

Before starting, make sure you have the following prerequisites met:

You have Pulumi installed and configured on your local machine.
You have the OCI CLI configured with the necessary API keys and permissions.
You have kubectl configured to interact with your OKE cluster.
You have GitLab Runner Helm chart values prepared, either in a YAML file or as a configuration object.

Now, here's the Pulumi TypeScript program that deploys the GitLab Runner Helm chart to your OKE cluster:

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

// The following configs are required for deploying the GitLab Runner.
// Make sure to replace them with your correct cluster details.
const clusterName = "your-cluster-name"; // Replace with your OKE cluster name
const kubeconfig = "your-kubeconfig"; // Replace with your OKE cluster kubeconfig data

// Create a Pulumi Kubernetes provider using the kubeconfig from Oracle Kubernetes Engine (OKE)
const provider = new k8s.Provider("oke-k8s-provider", {
    kubeconfig: kubeconfig, // Assumes this kubeconfig is properly configured to access your OKE cluster
});

// Deploy the GitLab Runner using a Helm Chart
const gitlabRunner = new k8s.helm.v3.Chart("gitlab-runner", {
    chart: "gitlab-runner",
    version: "0.12.0", // Specify the chart version you want to deploy
    fetchOpts: {
        repo: "https://charts.gitlab.io/", // This is the repository where the GitLab Runner Helm chart is hosted
    },
    // Values for the GitLab Runner chart. These can be fetched from the chart's README or the desired values.yaml file.
    values: {
        gitlabUrl: "https://gitlab.your-company.com/", // Replace with your GitLab instance URL
        runnerRegistrationToken: "your-registration-token", // Replace with your GitLab runner registration token
        // Add any additional custom configurations specific to your setup here.
    },
}, { provider: provider }); // Important: Specify the provider to ensure Helm uses the correct cluster

// Lastly, if you need to access the GitLab Runner service from outside the cluster,
// you'll need to export the service name or endpoint URL after deploying it.

export const gitlabRunnerServiceName = gitlabRunner.getResourceProperty("v1/Service", "gitlab-runner", "metadata").apply(m => m.name);

This program accomplishes the following:

Sets up a Kubernetes provider to communicate with your OKE cluster using the kubeconfig details.
Deploys the GitLab Runner Helm chart to the OKE cluster. The values object in the Chart resource should be configured according to your specific GitLab Runner configuration. For complete configuration options, visit the official GitLab Runner Helm chart documentation.
Optionally exports the name of the GitLab Runner service, which can be used to access or refer to the service within your Kubernetes cluster.

Please replace the placeholder variables with your actual configuration details for the OKE cluster name, kubeconfig data, GitLab URL, and registration token. Further customizations may be required based on your specific setup or requirements for GitLab Runner.

After setting up the program, save it to a file (e.g., index.ts), and then run it using the Pulumi CLI:

pulumi up

This command will prompt you to preview the changes and then execute the deployment to your Oracle Kubernetes Engine cluster. Once completed, the GitLab Runner will be deployed and running according to the Helm chart's specifications.