Deploy the identity helm chart on Oracle Kubernetes Engine (OKE)

Question

Pulumi · Accepted Answer

Deploying the Identity Helm Chart on Oracle Kubernetes Engine (OKE) requires several steps, which include setting up the OKE cluster, configuring Helm for use with the Kubernetes cluster, and finally deploying the chart itself.

Here's a step-by-step guide along with a Pulumi TypeScript program that accomplishes this:

1. Create an OCI Container Engine for Kubernetes (OKE) cluster. This will be the environment where your applications are deployed.
2. Ensure that Helm is installed and configured to work with your Kubernetes cluster.
3. Use the Helm Chart resource in Pulumi to deploy the Identity Helm Chart.

Below is the Pulumi TypeScript program implementing these steps. Be sure you have Oracle Cloud Infrastructure (OCI) provider configured with your credentials.

```typescript
import * as pulumi from '@pulumi/pulumi';
import * as oci from '@pulumi/oci';
import * as kubernetes from '@pulumi/kubernetes';

// Initialize a new OCI provider configuration with the given OCI region
const ociProvider = new oci.Provider('oci-provider', {
    region: 'us-ashburn-1', // Replace with your desired OCI region
});

// Step 1: Create an OKE cluster
const cluster = new oci.ContainerEngine.Cluster('oke-cluster', {
    // Provide your compartment ID
    compartmentId: ociProvider.compartmentId,
    // Specify the desired Kubernetes version
    kubernetesVersion: 'v1.21.5', // Update to the desired version
    // Define your VCN and other networking resources. Here we assume they are already created
    vcnId: 'ocid1.vcn.oc1.iad.amaaaaaaxxxx', // Replace with your actual VCN OCID
    options: {
        serviceLbSubnetIds: [
            'ocid1.subnet.oc1.iad.aaaaaaaaxxxxx', // Replace with your Load Balancer Subnet OCIDs
            'ocid1.subnet.oc1.iad.aaaaaaaaxxxxx',
        ],
        kubernetesNetworkConfig: {
            servicesCidr: '10.96.0.0/12',
            podsCidr: '10.244.0.0/16',
        },
        // Other options as needed
    },
    // Additional configurations like tags, if necessary
}, { provider: ociProvider });

// Setup the Kubernetes provider to deploy resources in the created OKE cluster
const k8sProvider = new kubernetes.Provider('k8s-provider', {
    kubeconfig: cluster.kubeconfig.apply(JSON.stringify),
});

// Step 2: Deploy the Identity Helm Chart using Helm provider
const identityHelmChart = new kubernetes.helm.v3.Chart('identity-chart', {
    chart: 'identity', // Replace with the name of the chart you want to deploy
    // The repository where your Helm chart is located
    fetchOpts: {
        repo: 'https://charts.mycompany.com/', // Update to the Helm repository URL
    },
    // The values to configure the chart with
    values: {
        // Key-value pairs here
    },
}, { provider: k8sProvider });

// Optionally, export the cluster endpoint
export const clusterEndpoint = cluster.endpoints.apply(e => e.private);

// Run `pulumi up` to deploy these resources to your OCI account
```

Replace the placeholders with the appropriate values. For example, you should specify the correct compartmentId, OCI region, VCN and subnet IDs, the Kubernetes version that you want, and the URL of the Helm repository hosting the Identity chart.

Here's what the code does:
- It initializes a new `oci.Provider` resource to communicate with the OCI API in your specific region.
- It creates a new `oci.ContainerEngine.Cluster` which represents the OKE cluster with a specified Kubernetes version and networking configuration.
- It sets up a `kubernetes.Provider` which is used to interact with the Kubernetes cluster once it's up and running.
- It deploys the Identity Helm chart using the `kubernetes.helm.v3.Chart` resource which fetches the chart from your specified repository and deploys it using the provided values.

You can run the program with `pulumi up`. Pulumi CLI will automatically pick up your OCI credentials and deploy the resources to your Oracle Cloud Infrastructure account. Remember to make sure your OCI CLI is correctly configured on your machine or in your CI/CD environment.