Humio Operator 0.34.0 GA (2026-01-20)

Version?Type?Release Date?Config.Changes?
0.34.0GA2026-01-20 

Version 0.34.0 significantly expands the operator's capabilities with advanced telemetry monitoring, package and package registry options, and event forwarder and event forwarding rules.

Removed

Items that have been removed as of this release.

Custom Resource Definition

  • Removed the HumioTelemetry CRD in favor of the new split telemetry architecture using HumioTelemetryCollection and HumioTelemetryExport resources.

New features and improvements

  • Configuration

    • Implemented version-aware Kafka configuration migration system to handle deprecated configuration options. The system provides automatic migration of legacy Kafka settings to supported configurations based on LogScale version compatibility.

  • Custom Resource Definition

    • Introduced package management capabilities with HumioPackageRegistry and HumioPackage CRDs. Supports multiple registry types including GitHub, GitLab, AWS S3, Google Cloud Storage, JFrog Artifactory, and LogScale Marketplace. Enables automated installation and management of LogScale packages through Kubernetes resources.

    • Added HumioEventForwarder and HumioEventForwardingRule CRDs for managing event forwarding configurations. These resources enable declarative configuration of event forwarding rules and destinations within LogScale clusters.

    • Added HumioSavedQuery Custom Resource Definition for managing LogScale saved queries through Kubernetes. The CRD supports Kubernetes Conditions for status reporting and enables declarative management of saved queries across LogScale clusters.

    • Replaced the previous HumioTelemetry CRD with a telemetry system featuring HumioTelemetryCollection and HumioTelemetryExport resources. The new system provides flexible data collection schedules, multiple export destinations, and status reporting for monitoring LogScale cluster usage and performance metrics.

Fixed in this release

  • Functions

    • Fixed query-capable node pool discovery when clusters use both main node pools and additional ingest-only node pools. The telemetry collector now correctly identifies and targets query-capable pods for LogScale API operations.