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.

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