Deploy the aws-container-insight-fluent-bit helm chart on Oracle Kubernetes Engine (OKE)

Question

Pulumi · Accepted Answer

Deploying a Helm chart on Oracle Kubernetes Engine (OKE) using Pulumi involves several steps. Since we're focusing on AWS container insights using Fluent Bit and the infrastructure is on Oracle Cloud Infrastructure (OCI), you'll first need to set up your Kubernetes cluster in OCI. Then you'll use the Pulumi Kubernetes provider to deploy the Helm chart.

To accomplish this, you'll need to do the following:

1. Create an instance of an OKE cluster using the `oci.ContainerEngine.Cluster` resource from the OCI package.
2. Configure `kubeconfig` so that Pulumi can communicate with your cluster.
3. Use the `kubernetes.helm.v3.Chart` resource to deploy the `aws-container-insight-fluent-bit` Helm chart on your OKE cluster.

Below is a Pulumi program written in TypeScript to deploy `aws-container-insight-fluent-bit` on an existing OKE cluster. Note that this assumes you have already configured Pulumi with your OCI credentials and have the required permissions to deploy resources.

First, you start by importing the necessary Pulumi and Kubernetes packages:

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

Next, you need to obtain the kubeconfig for your existing Oracle Kubernetes Engine cluster. This typically involves using the OCI API to fetch the cluster details and then constructing the kubeconfig file from those details. Here, we'll assume the kubeconfig is already set up and available on your local machine or through OCI secrets.

After you have the kubeconfig configured, you'll set up the Kubernetes provider:

```typescript
const provider = new k8s.Provider("oke-k8s", {
    kubeconfig: /* your kubeconfig here */,
});
```

Now you can define the Helm chart deployment:

```typescript
const chart = new k8s.helm.v3.Chart("aws-container-insight-fluent-bit", {
    chart: "aws-container-insight-fluent-bit",
    // You might need to specify the repository where the Helm chart is located, e.g.:
    // repo: "https://aws.github.io/eks-charts",
    version: "x.y.z", // specify the chart version
    namespace: "kube-system", // namespace to install the chart
    // values: { /* specify any configuration values for the chart */ },
}, { provider });
```

Note that you may also need to specify the Helm chart version and the Kubernetes namespace where the chart should be deployed. Additionally, you can provide custom configuration values if needed under the `values` field.

In the end, you may also want to export some information about the deployment, such as the namespace or the release name of the chart, for future reference:

```typescript
export const namespace = chart.namespace;
export const releaseName = chart.releaseName;
```

Here's the complete program:

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

// Set up Kubernetes provider using kubeconfig from your OKE cluster
const provider = new k8s.Provider("oke-k8s-provider", {
    kubeconfig: /* your kubeconfig here */,
});

// Deploy the aws-container-insight-fluent-bit Helm chart on OKE
const chart = new k8s.helm.v3.Chart("aws-container-insight-fluent-bit", {
    chart: "aws-container-insight-fluent-bit",
    version: "x.y.z", // Use the correct chart version
    namespace: "kube-system", // Deploy in the 'kube-system' namespace or the appropriate one
    // values: { /* Custom configurations for the Helm chart */ },
}, { provider });

// Output the namespace and release name, may be helpful for future commands
export const namespace = chart.namespace;
export const releaseName = chart.releaseName;
```

Please remember to replace the placeholder comments with actual values. The `kubeconfig` should be the configuration content or path that allows Pulumi to connect to your OKE cluster.

This program demonstrates the deployment of a Helm chart within Oracle Kubernetes Engine using Pulumi's TypeScript SDK. The chart name, version, and values need to be aligned with those provided by the Fluent Bit Helm chart in the respective Helm repository.