Running Humio on Kubernetes

If you are looking for information about shipping data from a Kubernetes cluster to Humio without running Humio in Kubernetes, please see our Kubernetes platform integration documentation.

Installation using Helm

The easiest way to install Humio in Kubernetes is to use the offical Humio helm charts.

Directions for installing Helm for your particular OS flavor can be found on the Helm GitHub page.

Once that is done, it will be necessary to update the main Helm chart repository. This main repository contains subcharts for Humio.

We depend on the Confluent Helm Charts as dependencies, which are included automatically when running the installation below.

helm repo add humio
helm repo update

Now create a values.yaml file with the following content

  enabled: true
  enabled: true
    autodiscovery: true
    fluentbit: {kubernetes: in-cluster}

These settings will tell Helm to create a default three-node Humio cluster with Kafka and Zookeeper. It will also create a Fluent Bit daemonset that will collect logs from any pods running in the Kubernetes cluster, and autodiscover the Humio endpoint and token. We recommend installing Humio into its own namespace; in this example we’re using the logging namespace

helm install -f values.yaml humio/humio-helm-charts --name humio --namespace logging

Logging in following installation

There are a few ways to get the URL for a Humio cluster. In most cases, grabbing the load balancer URL is sufficient

kubectl get service humio-humio-core-http -n logging -o go-template --template='http://{{(index .status.loadBalancer.ingress 0 ).ip}}:8080'

If you’re running in Minikube, run this command instead:

minikube service humio-humio-core-http -n logging --url

If humio-core.authenticationMethod is set to single-user (default), then you need to supply a username and password when logging in. The default username is developer and the password can be retrieved from the command

kubectl get secret developer-user-password -n logging -o=template --template={{.data.password}} | base64 -D

The base64 command may vary depending on OS and distribution.

Additonal Helm customization

It may be necessary to create a custom Helm values.yaml file to adjust from the default settings.

Below is an example of a custom values.yaml file with various customizations. For a full list of customizations, reference the Helm chart.

  enabled: true

  # Use 5 Humio nodes rather than the default of 3.
  replicas: 5

  # Disable single-user mode so Humio is open with no authentication.
  authenticationMethod: ""

  # Use a custom version of Humio.
  image: humio/humio-core:<version>

  # Custom bloomfilter options.
    enabled: true
    backfillingEnabled: true

  # Custom partitions
    initialPartitionsPerNode: 2
    initialPartitionsPerNode: 2

  # Custom CPU/Memory resources
     cpu: 2
     memory: 4Gi
     cpu: 2
     memory: 4Gi

  # Custom JVM memory settings
    xss: 4m
    xms: 512m
    xmx: 3072m

  # Custom Affinity Policies
        - matchExpressions:
          - key: node_type
            operator: In
            - humio

# Disable the fluentbit daemonset
  enabled: false

Upgrading with Kubernetes

For more information on steps to upgrade Humio with Kubernetes, see updating Humio.


This will destroy all Humio data.

helm delete --purge humio
kubectl delete namespace logging --cascade=true