Full Humio Operator Release Notes

This section contains a single page with all release notes on the same page.

Humio Operator 0.31.1 GA (2025-09-01)

Version?Type?Release Date?Config.Changes?
0.31.1GA2025-09-01 

This version fixes a bug in the cluster role that is set up in the helm chart which prevented installing 0.31.0

Humio Operator 0.31.0 GA (2025-08-25)

Version?Type?Release Date?Config.Changes?
0.31.0GA2025-08-25 

Version 0.31.0 adds support for a new CRD called HumioMultiClusterSearchView which can be used to set up and manage views using the LogScale multi cluster search functionality.

This version also addresses a bug that was introduced in version 0.27.0 where the operator did not properly handle multiple resource types when the user did not specify their own labels.

Humio Operator 0.30.0 GA (2025-07-14)

Version?Type?Release Date?Config.Changes?
0.30.0GA2025-07-14 

Fixes Pod Disruption Budget field validation and adds watchNamespace support into the helm chart.

Humio Operator 0.29.2 GA (2025-06-03)

Version?Type?Release Date?Config.Changes?
0.29.2GA2025-06-03 

Fixes a nil pointer issue when using update strategy RollingUpdateBestEffort.

Humio Operator 0.29.1 GA (2025-06-02)

Version?Type?Release Date?Config.Changes?
0.29.1GA2025-06-02 

Version 0.29.1 includes a bugfix for a bug introduced in version 0.29.0. It updates the ClusterRole used by humio-operator, so it allows accessing PersistentVolume resources. Prior to this fix, the humio-operator would fail trying to access the PersistentVolume resources as the Helm chart did not grant access to these.

Fixed in this release

  • Third Party Tooling

    • Add support for Kubernetes v1.33

    • Drop support for Kubernetes v1.25 and v1.26

Humio Operator 0.29.0 GA (2025-05-27)

Version?Type?Release Date?Config.Changes?
0.29.0GA2025-05-27 

This release introduces new CRDs for user/group/role management and feature flags, enhances validation, implements seamless upgrades, and includes several improvements and bug fixes.

New features and improvements

  • User, Group, and Role Management

    • Added new CRD HumioUser for managing users and their root status.

    • Added new CRD HumioGroup for managing groups and setting up the identity provider mapping name that maps to the groups.

    • Added new CRD's for roles (HumioSystemPermissionRole, HumioOrganizationPermissionRole, HumioViewPermissionRole): Enables creating roles with different permission types and assigning them to groups.

  • Updates

    • Improved RollingUpdateBestEffort behavior (credit: bderrly).

  • API

    • Enhanced validation using OpenAPI schema and CEL rules instead of reconciler-based validation, enabling pre-creation enforcement of object compliance.

  • Custom Resource Definition

    • Added HumioFeatureFlag CRD for toggling LogScale feature flags.

  • Other

    • Implemented managed fields tracking for seamless upgrades, preventing unnecessary pod replacements during future operator upgrades.

Fixed in this release

  • Security

    • Upgraded build dependencies to address CVEs and updated CI workflows.

  • API

    • Added TokenSecretAnnotations support to HumioIngestToken CRD.

  • Configuration

    • Added validation for duplicate EnvironmentVariables.

    • Added configurable requeue-period (credit: bderrly).

    • Fixed tolerations for HumioBootstrapToken onetime pod.

  • Custom Resource Definition

    • Ensured pods bind to PVCs on schedulable nodes (credit: HackToHell).

  • Other

    • Fixed finalizer bug causing stuck objects during deletion.

    • Fixed repository creation to use provided retention parameters (credit: bowens-stripe).

Humio Operator 0.28.2 GA (2025-03-24)

Version?Type?Release Date?Config.Changes?
0.28.2GA2025-03-24 

Version 0.28.1 no longer enabled the /metrics endpoint by default, which started causing issues as it was used for liveness and readiness probes. This release reenables the /metrics endpoint by default, and uses the more appropriate dedicated /healthz and /readyz API endpoints for liveness and readiness probes, respectively (credit: brads-au)

Fixed in this release

  • Other

    • Fix incompatibility running tests suite with latest version of Ginkgo.

Humio Operator 0.28.1 GA (2025-03-18)

Version?Type?Release Date?Config.Changes?
0.28.1GA2025-03-18 

This release has several fixes and updates.

Fixed in this release

  • Security

    • Bump default helper image to address CVE-2025-22870.

  • Third Party Tooling

    • Run golangci-lint.

    • Migrate kubebuilder to go/v4 plugin.

    • Bump golang.org/x/net from 0.33.0 to 0.37.0.

  • API

    • Fix bug where disabling node pool feature AllowedAPIRequestTypes not does remove OperatorInternal.

  • Other

    • Add ability to use bootstrap tokens from image secrets.

Humio Operator 0.28.0 GA (2025-03-03)

Version?Type?Release Date?Config.Changes?
0.28.0GA2025-03-03 

This release adds support for LogScale cluster down scaling, Kubernetes version 1.32, removes support for Kubernetes version 1.24, and does a couple of bug fixes and improvements.

Fixed in this release

  • Third Party Tooling

    • Upgrade to go-jose to v4.0.5

    • Upgrade to Go v1.23

    • Added support for Kubernetes version 1.32, removing support for version 1.24 and below.

  • Other

    • LogScale cluster down scaling support. The Humio Operator will now detect down scaling requests when the desired node count is lower than the actual node count. It will then start evicting cluster nodes, removing them once the eviction is completed. This operation is done for one node at a time. If the cluster has multiple node pools, the down scaling is done independently for each node pool. This requires a LogScale version of at least 1.173.0, and the enablement of the enableDownscalingFeature in the humioCluster spec as exemplified below:

      yaml
      featureFlags:
            enableDownscalingFeature: true

    • Fixed an issue where HumioClusterReconciler is stuck pinning an empty zone. We'll only pin a non-empty zone going forward, and if no zone information is available it will behave as it did previously, assuming update strategy uses the default MaxUnavailable value of 1.

    • Fixed a bug where HumioActionReconciler kept updating a webhook action due to difference in ordering of headers.

Humio Operator 0.27.2 GA (2025-02-13)

Version?Type?Release Date?Config.Changes?
0.27.2GA2025-02-13 

This release fixes an issue with missing permissions in the helm chart. Without this fix, the operator refuses to start up properly.

Humio Operator 0.27.1 GA (2025-02-06)

Version?Type?Release Date?Config.Changes?
0.27.1GA2025-02-06 

This release fixes an issue introduced in version 0.27.0 where create and update operations on parsers would fail when no tagFields are specified in the HumioParser object. It also fixes an issue where updates to rolePermissions, viewGroupPermissions or extraKafkaConfigs did not take effect. There's also new functionality that supports creation of PodDisruptionBudget objects with per node pool specific configs.

Humio Operator 0.27.0 GA (2025-01-15)

Version?Type?Release Date?Config.Changes?
0.27.0GA2025-01-15 

This release includes a range of changes. It overhauls the client integration between humio-operator and LogScale, bumps various dependencies during build, generates reference API documentation for CRDs, changes to logging format, API validation and small bug fixes.

Fixed in this release

  • API

    • Add API validation so that creating or updating some custom resources with certain invalid field values.

    • Overhaul the client used by humio-operator for interacting with LogScale API's. The new client is generated based on the GraphQL schema which makes it easier during development. This change bumps the minimum supported LogScale version to 1.130.0.

    • Autogenerate Markdown reference API documentation for custom resource definitions. The generated markdown is output to a docs directory within the humio-operator source code.

    • Refactor how the difference is logged out when a resource update is triggered. Going forward, the diff field contains a map of key-value pairs with all the differences resulting in the update.

  • Other

    • Fixed a bug where pod creations would try reusing an existing pod name. In this scenario, it would error out and retry and the retry would use a different pod name and succeed.

Humio Operator 0.26.0 GA (2024-11-05)

Version?Type?Release Date?Config.Changes?
0.26.0GA2024-11-05 

Adds new options to update strategy as well as testing improvements. Removes unused /tmp volume. Note that upgrading to this version will cause all humio pods to restart.

Fixed in this release

  • Other

    • Add support for Kubernetes 1.30 and 1.31.

    • Add options enableZoneAwareness and maxUnavailable to update strategy. Defaults for enableZoneAwareness and maxUnavailable are true and 1, respectively. With this feature, the zone is pinned when doing pod replacements for a given node pool to ensure all pods in a given zone is replaced before moving on to the next zone. The maxUnavailable option allows either an absolute number, or a percentage of the nodeCount.

    • Various improvements to testing.

    • Removed unused /tmp volume and volume mount.

Humio Operator 0.25.0 GA (2024-09-17)

Version?Type?Release Date?Config.Changes?
0.25.0GA2024-09-17 

Adds new HumioBootstrapToken type for the operator to authenticate to the cluster, requirement for non-empty resource names, testing improvements. Removes the auth sidecar container. Note that upgrading to this version will cause all humio pods to restart.

Fixed in this release

  • Other

    • Includes support for the HumioBootstrapToken, which sets BOOTSTRAP_ROOT_TOKEN_HASHED on the humio pods which is then used by the operator for authentication to the cluster. This removes the need for the auth sidecar container as well as the auth serivce account. The authServiceAccountName field is now deprecated.

    • Various improvements to testing.

    • Require non-empty names for resources such as Actions, Aggregate Alerts, Alerts, FilterAlerts, IngestTokens, Parsers, ScheduledSeaches, Views.

Humio Operator 0.24.0 GA (2024-08-26)

Version?Type?Release Date?Config.Changes?
0.24.0GA2024-08-26 

This release includes support for new LogScale functionality, removes unused code and reworks how the operator tests are performed.

Fixed in this release

  • Other

    • Move operator API calls to LogScale to a new Kubernetes Service object. This new service object allows users to specify if pods should be included in the targets. Each node pool configuration now contains support for a field nodePoolFeatures includes a field allowedAPIRequestTypes that can be set to [] to exclude pods from that node pool from this service. The default value for allowedAPIRequestTypes is [OperatorInternal].

    • Rework mock client used during tests and bump various dependencies during build.

    • Added CRD's for aggregate alerts and scheduled searches.

    • Added extraHostnames field to TLS configuration to allow users to specify a list of additional hostnames they want to be appended in the TLS certificates.

    • Fix bug where the operator sometimes created new pods with the wrong pod revision annotation during pod replacements.

    • Removed unused node ID label for pods and persistent volume claims.

    • Ensure custom resources are requeued for reconcile after 15 seconds when no work is detected. This fixes a range of cases where objects are not properly reconciled periodically if e.g. external entities change. Previously a restart of the operator would kick off a new reconciliation, but with this change this is no longer needed.

Humio Operator 0.23.0 GA (2024-07-11)

Version?Type?Release Date?Config.Changes?
0.23.0GA2024-07-11 

This is a small release and includes support for Filter Alerts and support for fetching sensitive parts of actions from secrets.

Fixed in this release

  • Other

    • Add support for fetching sensitive parts of actions from secrets.

    • Add support for Filter Alerts.

Humio Operator 0.22.0 GA (2024-06-25)

Version?Type?Release Date?Config.Changes?
0.22.0GA2024-06-25 

This is a small release and mostly fixes a few smaller bugs, leverages the LogScale parser V2 API and a handful of changes to how the operator itself is built and tested.

Fixed in this release

  • Other

    • Assume latest version of LogScale cluster pods if image tag cannot be properly parsed.

    • Fix bug where targetPort for Kubernetes Service object was not set to the container port of LogScale cluster pods.

    • Fix bug that caused parser update calls when a HumioParser custom resource did not contain any value for TagFields or TestData.

    • Use the new LogScale parser V2 API when creating and updating parsers.

Humio Operator 0.21.0 GA (2024-05-08)

Version?Type?Release Date?Config.Changes?
0.21.0GA2024-05-08 

This introduces changes to the set of environment variables for pods and will cause cluster pod restarts to roll this out. The bump to minimum supported LogScale version includes cleaning up a bunch of legacy behavior. This introduces a new field named CommonEnvironmentVariables which is a common set of environment variables that all cluster pods should inherit.

Fixed in this release

  • Third Party Tooling

    • Upgrade to Go v1.22

    • Upgrade to controller-gen v0.14.0

    • Upgrade various smaller dependencies

  • Other

    • Refactor test execution

    • Add support for HumioCluster.Spec.CommonEnvironmentVariables. This provides a way of defining a common set of environment variables that all cluster pods will inherit. If a node pool explicitly sets the same environment variable, then the node pool specific value takes presedence over the specified common environment variables (credit: bderrly)

    • Bump minimum supported version to LogScale 1.118.0

    • Ignore NodeName and VolumeMount with prefix "kube-api-access-" when logging podSpecDiff

    • Add test coverage for Kubernetes 1.28 and 1.29

Humio Operator 0.20.3 GA (2024-03-18)

Version?Type?Release Date?Config.Changes?
0.20.3GA2024-03-18 

Fixed in this release

  • Other

    • Fixes a bug where the humio-operator will not properly run the upgrade tasks for a HumioCluster resource when that HumioCluster has been migrated to use only node pools, or when a node pool has been removed as part of an upgrade.

    • Ignore RunAsUserID and QueryOwnershipType when handling alerts.

Humio Operator 0.20.2 GA (2024-01-31)

Version?Type?Release Date?Config.Changes?
0.20.2GA2024-01-31 

Fixed in this release

  • Other

    • Adds identifier to log events from humio-operator to have a stable ID for Kubernetes objects it is reconciling.

    • Fixes a bug where the humio-operator may mistakenly see a LogScale repository as empty during LogScale pod restarts. It is now required to explicitly set AllowDataDeletion to true for a given HumioRepository object if the humio-operator is allowed to do actions that may delete data in a LogScale repository by either lowering retention settings or by deleting the repository entirely.

Humio Operator 0.20.1 GA (2023-11-16)

Version?Type?Release Date?Config.Changes?
0.20.1GA2023-11-16 

Fixed in this release

  • Other

    • Small fix for helm chart when trying to define operator.nodeSelector in the values.yaml file.

    • There is a fix for updating connections for a HumioView resource.

    • The baked in logic for OpenShift SecurityContextContaints was removed, as it's been stale for a while and isn't being covered by the tests.

    • Fix bug where we tried updating ServiceAccount annotations before the ServiceAccount was created.

    • Fix bug where pods were restarted in a rolling fashion when updateStrategy was set to ReplaceAllOnUpdate and the change did not include a version upgrade.

    • Minimum logscale version was bumped to 1.100.0.

    • Various dependency upgrades for fixing various deprecations. Most notably an issues which bumps the helper image, which will cause all pods to get restarted to update them to use the new helper image.

Humio Operator 0.20.0 GA (2023-09-06)

Version?Type?Release Date?Config.Changes?
0.20.0GA2023-09-06 

Fixed in this release

  • Other

    • Bump humio/cli dependency to use new graphql library.

    • Add support for role-permissions.json file and mark use of view-group-permissions.json as deprecated. Official docs on the feature: Set up roles in a file

    • Skip creating a Kubernetes service for node pools of size 0.

    • Include all environment variable sources when getting environment variable sources. Prior to this, changes to environment variable sources were only detected using the first entry found, causing no changes to be detected if there is multiple of them.

    • Bump version with automatic partition management on by default to 1.89.0, and skip automatically configuring ZooKeeper node UUID URL for new LogScale versions.

    • Change default nodeCount from 3 to 0. This means the user now has to explicitly set the desired nodeCount instead of relying on a default value.

Humio Operator 0.19.1 GA (2023-08-30)

Version?Type?Release Date?Config.Changes?
0.19.1GA2023-08-30 

Fixed in this release

  • Other

    • Fixes an issue where permissions to HumioAlerts and HumioActions are not included when using the watchNamespaces flag when installing the operator using the operator helm chart.

Humio Operator 0.19.0 GA (2023-05-18)

Version?Type?Release Date?Config.Changes?
0.19.0GA2023-05-18 

This release removes automatic setting of HUMIO_GC_OPTS, disables deprecated calls to the LogScale API, and adds support for custom PriorityClass on pods. Due to the default changes to the HUMIO_GC_OPTS environment variable, upgrades of the operator to this version will cause humio pods to be restarted. Additionally, there were changes to certificates for TLS-enabled clusters, which upon upgrade of the operator will also cause restarts of the humio pods.

Fixed in this release

  • Other

    • Disable deprecated calls to the LogScale API.

    • Remove automatic setting of HUMIO_GC_OPTS. Relies on the defaults set by LogScale. It's still possible to set HUMIO_GC_OPTS via environmentVariables.

    • Support for PriorityClass.

Humio Operator 0.18.0 GA (2023-04-06)

Version?Type?Release Date?Config.Changes?
0.18.0GA2023-04-06 

This release adds support for ThrottleField to HumioAlert types, adds support for TopologySpreadConstraints, updates various dependencies, adds validation for Kubernettes 1.25 and adds support for additional chart labels.

Fixed in this release

  • Other

    • Validation of support for Kubernetes 1.25.

    • Support for TopologySpreadConstraints.

    • Refactor of chart labels and allow additional common labels (credit: gawa).

    • RollingUpdateBestEffort update strategy no longer dependent on stable or minor version differences.

    • Update several go module dependencies.

Humio Operator 0.17.0 GA (2023-02-06)

Version?Type?Release Date?Config.Changes?
0.17.0GA2023-02-06 

This release contains support for LogScale 1.70.0+, where fetching UUIDs from ZooKeeper is now deprecated. With this operator release, it's now possible to remove the ZOOKEEPER_URL environment variable. Upgrade to this release if running LogScale 1.70.x+.

Fixed in this release

  • Other

    • No longer set KAFKA_MANAGED_BY_HUMIO=true as true is the default.

    • Support for removal of ZOOKEEPER_URL.

    • Update several go module dependencies.

Humio Operator 0.16.0 GA (2022-11-07)

Version?Type?Release Date?Config.Changes?
0.16.0GA2022-11-07 

This release contains a number of fixes and updates, as well as a beta feature that allows for local PVCs. This release also bumps the default helper container image as well as changes the container names in the pod, which will cause cluster pods to be recreated when the operator is upgraded. This release requires LogScale version of 1.51.x or greater.

Fixed in this release

  • Other

    • Remove NET_BIND_SERVICE from the humio container. Requires LogScale 1.51.x+.

    • Remove NET_BIND_SERVICE from the operator pod and make the filesystem readonly. Move runAsNonRoot from the operator pod level to the container level.

    • Faster replacement of pods during upgrades. Rather than creating pods incrementally during an upgrade, all pods are now created simultaneously.

    • Prefix sidecar container names with humio-.

    • Add LogScalePersistentVolumeClaimPolicy with ReclaimType of OnNodeDelete, which allows automatic cleanup of PVCs when using a local volume provisioner.

Humio Operator 0.15.0 GA (2022-07-19)

Version?Type?Release Date?Config.Changes?
0.15.0GA2022-07-19 

This release contains a number of small fixes and updates.

Fixed in this release

  • Other

    • Add minReadySeconds which sets the minimum time in seconds that a pod must be ready before the next pod can be deleted when doing rolling update.

    • Remove --installCRDs command from helm and use helm3 best practices using the --skip-crds flag. Removes support for helm2.

Humio Operator 0.14.2 GA (2022-04-19)

Version?Type?Release Date?Config.Changes?
0.14.2GA2022-04-19 

This release contains a number of small fixes and updates.

Fixed in this release

  • Other

    • Add support for pod annotations in the chart (credit: kmjayadeep)

    • Fixes a bug where using imageSource may deploy an incorrect version of LogScale

    • Updates a number of dependencies

    • Updates the operator to use a scratch base image resulting in a smaller image size

Humio Operator 0.14.1 GA (2022-02-09)

Version?Type?Release Date?Config.Changes?
0.14.1GA2022-02-09 

This release updates the LogScale client so it no longer uses a deprecated API endpoint that is removed in LogScale 1.37.0. It is recommended to upgrade to this release prior to upgrading to LogScale 1.37.0.

Humio Operator 0.14.0 GA (2022-02-01)

Version?Type?Release Date?Config.Changes?
0.14.0GA2022-02-01 

This release introduces support for Node Pools, upgrade strategy options for LogScale upgrades, and adds a headless service for intra cluster communication. Deploying this release will cause all LogScale pods to be restarted simultaneously due to the migration to the headless service.

Fixed in this release

  • Other

    • Fixes issue where LogScale pods that have been evicted are not re-created

    • Adds upgrade strategies that allow for rolling upgrades of LogScale

    • Adds support for Node Pools, so different LogScale nodes can be split out by configuration. For example, to allow for ingest-only nodes

    • Adds feature to auto-detect the cores available to the LogScale container, so the resources for the pod may be omitted

    • Adds support for automatically detecting processor count when no resource limits are set

    • Fixes issue where the operator does not always retry when failing to create LogScale resources (HumioParser, HumioView, HumioRepository)

    • The --server-side flag is now required when running kubectl apply on the HumioCluster CRD due to its size

    • Fixes issue where LogScale pods that are pending can not updated

Humio Operator 0.13.0 GA (2021-11-09)

Version?Type?Release Date?Config.Changes?
0.13.0GA2021-11-09 

This release bumps the default helper container image, which will cause cluster pods to be recreated when the operator gets upgraded in order to leverage the new helper image tag. If recreation of pods is undesired it is possible to lock the helper image by setting helperImage in the HumioCluster resource to the current version before upgrading the operator. If the helper image tag gets locked, we recommend removing this explicit helper image tag during the next LogScale cluster upgrade.

Fixed in this release

  • Other

    • Fixes multiple bugs where the controller performs unnecessary reconciles resulting in high CPU usage

    • Fixes bug where a HumioView is updated on every reconcile even when it hasn't changed (credit: Crevil)

Humio Operator 0.12.0 GA (2021-10-11)

Version?Type?Release Date?Config.Changes?
0.12.0GA2021-10-11 

Fixed in this release

  • Other

    • Updates cert manager api to use cert-manager.io/v1 instead of cert-manager.io/v1beta1

    • Adds feature to specify secret references for certain fields of HumioAction resources (credit: Crevil)

    • Fixes a number of conflicts where the operator attempts to update old versions of resources it manages

    • Fixes issue where the operator may become stuck when the LogScale cluster does not respond to requests

    • Fixes issue where the livenessProbe and readinessProbe on the LogScale pods may fail and cause a cascading failure

    • Adds feature to pull the value of LogScale pod's environment variables from a configmap or secret

    • Adds a startupProbe to the LogScale pods

    • Mounts the LogScale pod's tmp volume under the same container mount that is used for the humio-data directory (applies to LogScale versions 1.33.0+)

    • Adds feature to pull the value of a LogScale image from a configmap

Humio Operator 0.11.0 GA (2021-09-14)

Version?Type?Release Date?Config.Changes?
0.11.0GA2021-09-14 

Fixed in this release

  • Other

    • Fixes a bug where pods may not be created as quickly as they should during an upgrade or restart of LogScale.

    • Improved logging

Humio Operator 0.10.2 GA (2021-08-24)

Version?Type?Release Date?Config.Changes?
0.10.2GA2021-08-24 

Version 0.10.2 of the operator no longer works for Kubernetes versions prior to 1.19. This is because the operator now uses the networking/v1 api which does not exist in Kubernetes 1.18 and older.

Fixed in this release

  • Other

    • Uses networking/v1 instead of the deprecated networking/v1beta1

    • Updates the default humio version to 1.28.0

    • Fix bug around installing and validating license when running multiple HumioClusters

Humio Operator 0.10.1 GA (2021-07-27)

Version?Type?Release Date?Config.Changes?
0.10.1GA2021-07-27 

Version 0.10.0 was released with the default operator image tag version 0.9.1, while the intention was to use the default image tag of 0.10.0. This release fixes that so the new default image becomes 0.10.1 which includes all the fixes described in the notes for 0.10.0.

Humio Operator 0.10.0 GA (2021-07-08)

Version?Type?Release Date?Config.Changes?
0.10.0GA2021-07-08 

This release bumps the default helper container image, which will cause cluster pods to be recreated when the operator gets upgraded in order to leverage the new helper image tag. If recreation of pods is undesired it is possible to lock the helper image by setting helperImage in the HumioCluster resource to the current version before upgrading the operator. If the helper image tag gets locked, we recommend removing this explicit helper image tag during the next LogScale cluster upgrade.

Fixed in this release

  • Other

    • Sidecar now reuses HTTP connections when possible for communicating with the LogScale API

    • Operator now reuses HTTP connections when possible for communicating with the LogScale API

Humio Operator 0.9.1 GA (2021-06-18)

Version?Type?Release Date?Config.Changes?
0.9.1GA2021-06-18 

No changes, see release notes for version 0.9.0.

Humio Operator 0.9.0 GA (2021-06-18)

Version?Type?Release Date?Config.Changes?
0.9.0GA2021-06-18 

This release drops support for LogScale versions prior to LogScale 1.26.0 and speeds up cluster bootstrapping significantly. With this release Bootstrapping state for HumioCluster CRD's have been removed entirely, so before upgrading to this release it is important to make sure that no HumioCluster resource is in Bootstrapping state.

This release also bumps the default helper container image, which will cause cluster pods to be recreated when the operator gets upgraded in order to leverage the new helper image tag. If recreation of pods is undesired it is possible to lock the helper image by setting helperImage in the HumioCluster resource to the current version before upgrading the operator. If the helper image tag gets locked, we recommend removing this explicit helper image tag during the next LogScale cluster upgrade.

Fixed in this release

  • Other

    • Bugfix so LogScale storage and digest partition counts are correct when new clusters gets created. Previously clusters would create storage and digest partitions based on LogScale's built-in defaults rather than the user-defined values storagePartitionsCount and digestPartitionsCount in the HumioCluster resource.

    • Drop the use of Bootstrapping state for HumioCluster resources.

    • Drop support for LogScale versions prior to 1.26.0.

    • Bugfix where license update is triggered even if license was not changed.

    • Bugfix liveness and readiness probes for HumioCluster CRD so it is now possible to set an empty probe. If an empty probe is used the operator will skip configuring the specific probe.

    • Switch operator container logs to RFC 3339 format with second precision. LogScale container logs are unaffected, as this only changes the logs from the operator container.

    • Set more detailed release version, commit and date. This version information is logged out during container startup, and is also set as a custom User-Agent HTTP header for requests to the LogScale API.

    • Additional logging for HumioExternalCluster when the API token test fails. Previously it would silently fail and the HumioExternalCluster would be stuck in Unknown state.

Humio Operator 0.8.1 GA (2021-05-26)

Version?Type?Release Date?Config.Changes?
0.8.1GA2021-05-26 

This release contains a fix for installing the LogScale license during the Bootstrapping state for the HumioCluster CRD.

Humio Operator 0.8.0 GA (2021-05-19)

Version?Type?Release Date?Config.Changes?
0.8.0GA2021-05-19 

This release adds support for LogScale 1.26.0 and newer. Upgrading to LogScale 1.26.0 is not supported with humio-operator versions prior to 0.8.0.

Fixed in this release

  • Other

    • License is now a required field on the HumioCluster resources. This must be present for both existing clusters and for bootstrapping new clusters.

    • Default LogScale image tag version has been updated to 1.24.3.

Humio Operator 0.7.0 GA (2021-05-11)

Version?Type?Release Date?Config.Changes?
0.7.0GA2021-05-11 

This release contains small bug fixes, exposes LogScale liveness and readiness probes, and updates operator-sdk and supporting tooling.

Fixed in this release

  • Other

    • Fixes bug where the operator will try to clean up CA Issuer even when not using cert-manager, resulting in logged warnings;

    • Allows overriding of LogScale liveness and readiness probes;

    • Fixes a bug where the HumioCluster may get stuck in a ConfigError state even when the cluster is healthy; and

    • Fixes bug where the operator may panic when the LogScale pods are down.

Humio Operator 0.6.1 GA (2021-03-16)

Version?Type?Release Date?Config.Changes?
0.6.1GA2021-03-16 

This release fixed a bug where the RBAC rules in the Helm chart have not been updated to include the new CRDs introduced in version 0.6.0.

Humio Operator 0.6.0 GA (2021-03-15)

Version?Type?Release Date?Config.Changes?
0.6.0GA2021-03-15 

This release contains new HumioAlert and HumioAction custom resources. This means these new CRDs must be applied before the upgrade, although it's recommended to apply CRDs during every upgrade.

Fixed in this release

  • Other

    • Adds LogScale Alerts and Actions support.

    • Adds the ability to the lookup hostname from a secret.

Humio Operator 0.5.1 GA (2021-02-26)

Version?Type?Release Date?Config.Changes?
0.5.1GA2021-02-26 

This release fixes a bug where ingress resources may still be created when spec.hostname and spec.esHostname are not set.

Humio Operator 0.5.0 GA (2021-02-04)

Version?Type?Release Date?Config.Changes?
0.5.0GA2021-02-04 

Fixed in this release

  • Other

    • The default LogScale version has been updated to 1.20.1.

    • The default json log format for LogScale has changed if running LogScale version 1.20.1 or later. See LogScale Internal Logging.

    • Upgrading to this release will replace the current HumioCluster pods.

Humio Operator 0.4.0 GA (2021-02-02)

Version?Type?Release Date?Config.Changes?
0.4.0GA2021-02-02 

Fixed in this release

  • Other

    • Fix for bug where partitions may not be auto balanced by the operator

    • Allow for additional labels for ingest token secrets

    • Requires explicitly defined storage. See below for additional information.

    • Adds support for managing LogScale licenses.

    • Change default humio version to 1.18.1

    • Symptoms of the fixed UUID bug when not using USING_EPHEMERAL_DISKS=true include the appearance of missing nodes and nodes with no partitions assigned in the Cluster Administration page in the LogScale UI.

    • Upgrading to this release will replace the current HumioCluster pods.

    • It is now required to explicitly define the storage configuration. This is because until now, the default has been emptyDir, which will result in loss of data if not also using bucket storage. If relying on the default storage configuration, it is now required to set either spec.dataVolumeSource or spec.dataVolumePersistentVolumeClaimSpecTemplate. It is necessary to use either a persistent storage medium or bucket storage to avoid data loss. See the example resources section on how to configure ephemeral or persistent storage.

    • Fix for bug where UUIDs are not assigned properly when not using USING_EPHEMERAL_DISKS=true. See below for additional information.

    • Updates to various operator-managed resources so they now include the ConfigError state

    • Fix to rolling restart logic to ensure that pods are only restarted one at a time

    • Fix bug where restart or update may fail if an existing pod is not in a Running state

Humio Operator 0.3.0 GA (2020-12-02)

Version?Type?Release Date?Config.Changes?
0.3.0GA2020-12-02 

Fixed in this release

  • Other

    • Add support for LogScale 1.19.0. LogScale 1.19.0 introduces some changes to how logging is performed which is not taken into account for humio-operator versions prior to this release.

    • New field added to HumioCluster CRD: disableInitContainer

      The init container is used to extract information about the availability zone from the Kubernetes worker node.

      When running in a single availability zone setup, it could make sense to disable the use of the init container to tighten up the permissions needed to run the pods of a HumioCluster.

    • New field added to HumioCluster CRD: helperImage

      This field makes it possible to override the default container image used for the helper image. This is useful in scenarios where images should be pulled from a local container image registry.

    • Leverage new suggested partition layouts

      With LogScale 1.17.0+ we will now rely on LogScale to suggest partition layouts for both digest and storage partitions. The benefit of doing this is that the suggested partition layouts will take into account what availability zone the LogScale cluster nodes are located in.

    • New field added to HumioCluster CRD: terminationGracePeriodSeconds

      Previously pods were created without an explicit termination grace period for pods. This meant that pods inherit the Kubernetes default behaviour which is 30 seconds. In general LogScale should be able to gracefully terminate by itself, and when running with bucket storage and ephemeral nodes the termination should allow time for the LogScale node to upload data to bucket storage. The new default value is 300 seconds, but can be overridden by using this field.

    • Bump default LogScale version to 1.18.0

      If the Image property on the HumioCluster is left out, this means that the cluster will get upgraded. Make sure to read the Humio Server 1.18.0 LTS (2020-11-26) to confirm this migration is safe to do.

    • Upgrading to this release will replace the current HumioCluster pods.

Humio Operator 0.2.0 GA (2020-11-13)

Version?Type?Release Date?Config.Changes?
0.2.0GA2020-11-13 

There is a new HumioView custom resource. This means the HumioView CRD must be applied before the upgrade (though it is recommended to apply CRDs during every upgrade). There are a number of new features and bug fixes in this release, which are described in the Release Notes.

Humio Operator 0.1.2 GA (2020-11-02)

Version?Type?Release Date?Config.Changes?
0.1.2GA2020-11-02 

This release fixes a bug where LogScale nodes using persistent storage may receive a NodeExists error when starting up. This applies to LogScale clusters using persistent storage, and not clusters using ephemeral disks and bucket storage.

If your cluster is using persistent storage (for example, Persistent Volume Claims), it is important to either omit the environment variable USING_EPHEMERAL_DISKS or set it to false.

If your cluster is using ephemeral disks and bucket storage, it is important to set the environment variable USING_EPHEMERAL_DISKS to true. This setting is included in the example resources.

This version also upgrades the helper image which is used as the init container and sidecar container for pods tied to a HumioCluster resource. This will be treated as an upgrade procedure, so all pods will be replaced.

Humio Operator 0.1.1 GA (2020-11-02)

Version?Type?Release Date?Config.Changes?
0.1.1GA2020-11-02 

No changes required.

Humio Operator 0.1.0 GA (2020-10-28)

Version?Type?Release Date?Config.Changes?
0.1.0GA2020-10-28 

No changes required, but it is important to note this version upgrades the helper image which is used as the init container and sidecar container for pods tied to a HumioCluster resource. This will be treated as an upgrade procedure, so all pods will be replaced.

Humio Operator 0.0.14 GA (2020-10-14)

Version?Type?Release Date?Config.Changes?
0.0.14GA2020-10-14 

Version 0.0.14 of the Humio Operator contains changes related to how Node UUIDs are set. This fixes an issue where pods may lose their node identity and show as red/missing in the LogScale Cluster Administration page under Cluster Nodes when they are scheduled in different availability zones.

When upgrading to version 0.0.14 of the Humio Operator, it is necessary to add the following to the HumioCluster spec to maintain compatibility with previous versions of how the Operator set UUID prefixes:

yaml
spec:
  nodeUUIDPrefix: "humio_{{.Zone}}_"

This change must be completed in the following order:

  • Shut down the Humio Operator by deleting it. This can be done by running: kubectl delete deployment humio-operator -n humio-operator

  • Make the above node UUID change to the HumioCluster spec

  • Upgrade the Humio Operator

If creating a fresh LogScale cluster, the nodeUUIDPrefix field should be left unset.

Migration to the new node UUID Prefix

The simplest way to migrate to the new UUID prefix is by starting with a fresh HumioCluster. Otherwise, the effect of this change depends on how the HumioCluster is configured.

If using S3 with ephemeral disks, humio nodes will lose their identity when scheduled to new nodes with fresh storage if this change is not made. If you'd like to migrate to the new node UUID prefix, ensure autoRebalancePartitions: false and then perform the upgrade. In the LogScale Cluster Administration page under Cluster Nodes, you will notice that old nodes show as red/missing and the new nodes do not have partitions. It is necessary to migrate the storage and digest partitions from the old nodes to the new nodes and then remove the old nodes. You may need to terminate the instance which contains the LogScale data one at a time so they generate new UUIDs. Ensure the partitions are migrated before terminating the next instance. Once all old nodes are removed, autoRebalancePartitions can be set back to true if desired.

If using PVCs, it is not strictly nescessary to adjust the nodeUUIDPrefix field as the node UUID is stored in the PVC. If the PVC is bound to a zone (such as with AWS), then this is not an issue. If the PVC is not bound to a zone, then you may still have the issue where nodes lose their pod identity when scheduled in different availability zones. If this is the case, nodes must be manually removed from the LogScale Cluster Administration page under Cluster Nodes, while taking care to first migrate storage and digest partitions away from the node prior to removing it from the cluster.

Humio Operator 0.0.13 GA (2020-10-13)

Version?Type?Release Date?Config.Changes?
0.0.13GA2020-10-13 

There are no special tasks required during this upgrade, however, it is worth noting that the operator-sdk version was changed in version 0.0.13 so it is important that the helm version matches the operator version otherwise the LogScale pods will fail to start due to a missing /manager entrypoint.

Humio Operator 0.0.12 GA (2020-09-08)

Version?Type?Release Date?Config.Changes?
0.0.12GA2020-09-08 

No special changes are necessary when upgrading the LogScale Operator between versions 0.0.0-0.0.11.

Fixed in this release

  • Updates

    • The selector labels changed in version 0.0.12, so for this reason it is necessary to delete the humio-operator deployment prior to upgrading the helm chart. The upgrade steps are:

      1. Delete the humio-operator deployment by running: kubectl delete deployment humio-operator -n humio-operator

      2. Run the helm upgrade command as documented above

      If the humio-operator deployment is not removed before the upgrade, the upgrade will fail with:

      syslog
      Error: UPGRADE FAILED: cannot patch "humio-operator" with kind Deployment: Deployment.apps "humio-operator" is invalid: spec.selector: Invalid value: v1.LabelSelector{MatchLabels:map[string]string{"app":"humio-operator", "app.kubernetes.io/instance":"humio-operator", "app.kubernetes.io/name":"humio-operator"}, MatchExpressions:[]v1.LabelSelectorRequirement(nil)}: field is immutable