Troubleshooting

Common issues with the Humio Operator are described in the following sections. For upgrade-specific troubleshooting, see Troubleshooting.

Reading Operator Logs

The operator controller manager logs are the first place to check when a cluster is not behaving as expected:

shell
# Follow operator logs
$ kubectl logs -n <operator-namespace> deployment/humio-operator-controller-manager -f

# View logs for a specific container
$ kubectl logs -n <operator-namespace> <controller-pod-name> -c manager

Cluster Stuck in ConfigError

A ConfigError state means the operator found an invalid or inconsistent configuration in the HumioCluster spec. The operator stops reconciling until the error is corrected.

To identify the error:

shell
$ kubectl describe humiocluster <cluster-name> -n <namespace>

Check the Status.Conditions and Status.Message fields in the output for a description of the error. After correcting the spec, the operator resumes reconciliation automatically.

Pods Failing to Start

If LogScale pods are failing to start, check the pod events and logs:

shell
# List pods and their status
$ kubectl get pods -n <namespace> -l app.kubernetes.io/name=humio

# Describe a failing pod
$ kubectl describe pod <pod-name> -n <namespace>

# View pod logs
$ kubectl logs <pod-name> -n <namespace> -c humio

Common causes include:

  • A missing or incorrectly named license secret. Verify that the secret referenced in spec.license.secretKeyRef.name exists in the same namespace.

  • A missing single-user password secret. If SINGLE_USER_PASSWORD is configured via a secretKeyRef, the secret must exist before the pod starts.

  • Insufficient node resources. Check that the resource requests and limits in the spec can be satisfied by the available Kubernetes worker nodes.

  • A storage volume that cannot be provisioned. Check persistent volume claim status with kubectl get pvc -n <namespace>.

TLS Certificate Issues

TLS is enabled by default. If pods cannot communicate or if cert-manager is not installed, TLS errors appear in the operator and pod logs.

  • Confirm that cert-manager is installed and its pods are running in the cluster.

  • Check whether Certificate resources have been created and are in a Ready state: kubectl get certificates -n <namespace>.

  • To disable TLS for testing, set spec.tls.enabled: false in the HumioCluster resource. See Configuring TLS with the Operator.

Configuration Resource Not Syncing

If a resource such as a HumioRepository or HumioParser is stuck in Unknown or NotFound state:

  1. Verify that the referenced cluster name in spec.managedClusterName matches an existing HumioCluster in the same namespace.

  2. Check that the target HumioCluster is in Running state before expecting configuration resources to sync.

  3. Check the operator logs for GraphQL API errors that indicate authentication failures or connectivity problems with the cluster.