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`.

Removed unused `/tmp` volume and volume mount.

Various improvements to testing.

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

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.

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.

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]`.

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

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.

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

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

Add support for Filter Alerts.

Add support for fetching sensitive parts of actions from secrets.

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

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

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

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

Bump minimum supported version to LogScale 1.118.0

Add test coverage for Kubernetes 1.28 and 1.29

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

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)

build: Upgrade to Go v1.22

build: Upgrade to controller-gen v0.14.0

build: Upgrade various smaller dependencies

test: Refactor test execution

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.

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.

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

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.

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

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

Minimum logscale version was bumped to 1.100.0.

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.

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.

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.

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

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.

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

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 humio/cli dependency to use new graphql library.

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.

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.

Disable deprecated calls to the LogScale API.

Support for PriorityClass.

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

Validation of support for Kubernetes 1.25.

Support for TopologySpreadConstraints.

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

Update several go module dependencies.

Support for removal of ZOOKEEPER_URL.

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

Update several go module dependencies.

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

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

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

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

Prefix sidecar container names with humio-.

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.

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

Updates a number of dependencies

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

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

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

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

Adds upgrade strategies that allow for rolling upgrades of LogScale

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

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

Fixes issue where LogScale pods that are pending can not updated

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 bug where a HumioView is updated on every reconcile even when it hasn't changed (credit: Crevil)

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

Adds a startupProbe to the LogScale pods

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

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

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

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

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

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+)

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

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

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

Improved logging

Updates the default humio version to 1.28.0

Uses networking/v1 instead of the deprecated networking/v1beta1

Fix bug around installing and validating license when running multiple HumioClusters

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.

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.

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

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

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

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

Change default humio version to 1.18.1

Allow for additional labels for ingest token secrets

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.

New field added to HumioCluster CRD: disableInitContainer

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

If enabled, the auto partition rebalancing will use this to assign digest and storage partitions with availability zones in mind.

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: 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.

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.

Shut down the LogScale 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 LogScale Operator