1. Deploy the gitea-instance helm chart on Oracle Kubernetes Engine (OKE)


    To deploy a helm chart on Kubernetes using Pulumi, you typically go through a few steps:

    1. Set up the Kubernetes Provider to communicate with your Kubernetes cluster.
    2. Use the Chart resource from the Pulumi Kubernetes provider to deploy your helm chart.

    Below is a step-by-step guide on how to deploy the gitea-instance helm chart on an Oracle Kubernetes Engine (OKE) cluster using Pulumi with TypeScript.


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

    • Pulumi CLI installed
    • Oracle Cloud Infrastructure (OCI) CLI configured
    • Access to an Oracle Kubernetes Engine (OKE) cluster

    Step 1: Set up a new Pulumi project

    Create a new directory for your Pulumi project and initialize a new project with pulumi new.

    mkdir pulumi-gitea-oke && cd pulumi-gitea-oke pulumi new typescript

    Step 2: Install the required Pulumi packages

    Install the Pulumi Kubernetes package that you'll use to interact with the Kubernetes API.

    npm install @pulumi/kubernetes

    Step 3: Write the Pulumi program

    Here, we are writing a Pulumi program to set up the Kubernetes provider to interact with OKE and then deploy the gitea-instance helm chart.

    import * as k8s from "@pulumi/kubernetes"; // Step 1: Configure the Kubernetes Provider to connect to your OKE cluster // You need to fetch the kubeconfig file from OCI to configure this correctly const kubeconfig = "my-kubeconfig-path"; // Replace with the path to your kubeconfig file const provider = new k8s.Provider("oke-k8s", { kubeconfig: kubeconfig, }); // Step 2: Deploy the Gitea helm chart to your OKE cluster using the provider defined above const giteaInstance = new k8s.helm.v3.Chart("gitea-instance", { chart: "gitea", version: "4.2.0", // Specify the version of the chart you want to deploy fetchOpts: { repo: "https://dl.gitea.io/charts/", // The chart repo URL where Gitea is located }, // Define any custom values you want to pass to your chart here // values: {}, }, { provider: provider }); // Optional: Export any output properties you'd like to later access export const giteaInstanceEndpoint = giteaInstance.getResourceProperty("v1/Service", "gitea-instance-gitea-http", "status").apply(status => status.loadBalancer.ingress[0].ip);


    1. Kubernetes Provider Setup: We first import the necessary Pulumi Kubernetes library. Then we create a Kubernetes provider instance by passing the path to our kubeconfig file, which describes how to connect to our Kubernetes cluster on OCI.

    2. Deploying Gitea via Helm Chart: We declare a new Helm chart resource for Gitea using k8s.helm.v3.Chart. We specify the name of the chart (gitea), the version we want to install, and the repository where the Helm chart is located. Optionally, you could specify custom configuration under the values option.

    3. Exporting Endpoint: After the deployment, we might want to access the service endpoint. We use export to output the service's IP address. This line uses the apply method to asynchronously fetch the necessary service information after it's been created by Pulumi.


    • Make sure the kubeconfig points to the correct cluster on OCI.
    • The version of the Helm chart should be updated to the desired version you want to deploy.
    • Additional customization of the Helm chart can be added to the values property if needed.

    After you have written this code, you would typically run pulumi up to start the deployment. Pulumi will provide you with a preview of resources to be created, and upon confirmation, will proceed with the deployment to your OKE cluster.