HumioCluster

A HumioCluster resource is the primary way to deploy and manage a LogScale cluster on Kubernetes using the Humio Operator. The operator reads the HumioCluster spec, creates the necessary Kubernetes resources (pods, services, secrets, certificates, ingress), and continuously reconciles the cluster to match the desired state.

Cluster states

The operator tracks the current state of a HumioCluster in the resource status. The following states are possible:

Running

All pods are running and the cluster is healthy.

Upgrading

The operator is replacing pods with an updated image. The behavior depends on the configured update strategy. See Update Strategy.

Restarting

The operator is restarting pods in response to a configuration change, such as an environment variable update.

ConfigError

The spec contains an invalid or inconsistent configuration. The operator logs the error and stops reconciling until the spec is corrected.

Pending

The operator is waiting for required resources to become available, such as a persistent volume or a referenced secret.

You can check the current state with:

shell
$ kubectl get humiocluster -n <namespace>

Spec structure

A HumioCluster spec has two levels of configuration:

  • Top-level spec fields apply to all pods when no node pools are defined, or to the default pool when node pools are present.

  • Node pool specs (spec.nodePools[].spec) override or extend the top-level spec for a specific group of pods. Each pool can have its own image, resource limits, environment variables, and storage configuration.

Fields common across all pools, such as the license and replication factor, are set at the top level. Fields that differ between pools, such as node role or storage class, are set in the pool spec.