Deploy the elastic-filebeat helm chart on Oracle Kubernetes Engine (OKE)

Question

Pulumi · Accepted Answer

To deploy the Elastic Filebeat Helm chart on Oracle Kubernetes Engine (OKE), you'll need to:

Set up an OKE cluster where you'll deploy the Helm chart.
Use the Helm chart to deploy Filebeat, which is a lightweight shipper for forwarding and centralizing log data.

Here's what you need to do step by step:

Set Up OKE Cluster: Ensure that you have created an OKE cluster in Oracle Cloud Infrastructure (OCI). This cluster provides the necessary Kubernetes infrastructure to facilitate the deployment. For setting up the OKE cluster using Pulumi, you would use the oci.ContainerEngine.Cluster resource.
Deploy Helm Chart: To deploy the Helm chart for Elastic Filebeat on your OKE cluster, you'd use the kubernetes.helm.v3.Chart resource from Pulumi's Kubernetes provider. This resource allows you to deploy Helm charts in Kubernetes clusters.

Here's a detailed program that deploys the Elastic Filebeat Helm chart to an existing OKE cluster:

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

// Ensure you have a kubeconfig file for your OKE cluster.
// Usually, this can be obtained from the Oracle Cloud Infrastructure console.
const kubeconfig = "<YOUR_KUBECONFIG_CONTENT>";

// Create a Provider to interact with your OKE cluster.
const provider = new k8s.Provider("oke-k8s", {
    kubeconfig: kubeconfig,
});

// Deploy the Elastic Filebeat Helm chart using the `Chart` resource.
const filebeatChart = new k8s.helm.v3.Chart("filebeat", {
    chart: "filebeat",
    version: "7.10.0", // Specify the version you want to deploy
    fetchOpts:{
        repo: "https://helm.elastic.co",
    },
    // Include any custom values you need for Filebeat's configuration.
    // Check the Filebeat Helm chart's values for configuration options.
    values: {
        filebeatConfig: {
            filebeat.yml: `
                filebeat.inputs:
                - type: log
                  paths:
                    - /var/log/*.log
                output.elasticsearch:
                  hosts: ["http://your-elastic-search-url:9200"]
            `,
        },
    },
}, { provider: provider }); // Specify the OKE cluster's provider.

// Export the Helm chart status
export const filebeatChartStatus = filebeatChart.status;

Make sure to replace "<YOUR_KUBECONFIG_CONTENT>" with the contents of your kubeconfig file. This file is what allows Pulumi to communicate with your cluster. You can get this information from your Oracle Cloud Infrastructure dashboard after setting up the OKE.
The version 7.10.0 is used as an example. You might need to specify the version of the Filebeat Helm chart that suits your requirements.
The filebeatConfig contains a basic configuration. You'll need to replace "http://your-elastic-search-url:9200" with the URL to your Elasticsearch instance where Filebeat will send the logs.

This will set up Filebeat in your cluster, and it will start shipping logs to your configured Elasticsearch instance. You can modify the configuration in the values field according to your requirements.

Remember to install the @pulumi/oci and @pulumi/kubernetes packages before running this program.

$ npm install @pulumi/oci @pulumi/kubernetes

After setting up and configuring the program, you can deploy it using the Pulumi CLI:

$ pulumi up

This command will execute the Pulumi program, and you should see the resources being created in the CLI output. After confirming the preview, Pulumi will deploy the Helm chart to your cluster.