0.92.0

What's Changed

• feat: support k8seventsreceiver by @thiemok in https://github.com/dash0hq/dash0-operator/pull/621
• fix(controller): use pagination when fetching workloads by @basti1302 in https://github.com/dash0hq/dash0-operator/pull/665
• fix(chart): set GOMEMLIMIT for operator manager by @basti1302 in https://github.com/dash0hq/dash0-operator/pull/667
• feat(target-allocator): add support for mTLS by @ten15bit in https://github.com/dash0hq/dash0-operator/pull/666
• chore: maintain our own target-allocator image by @ten15bit in https://github.com/dash0hq/dash0-operator/pull/669

Action Required

This Dash0 operator release allows setting GOMEMLIMIT for the operator manager. This setting was missing previously. This allows to better protect the operator from OutOfMemory errors. Since this is a new setting, its default value (205MiB) is set with respect to the operator’s default value for its own Kubernetes memory limit.

If you have set a custom operator.managerContainerResources.limits.memory you should also set a matching operator.managerContainerResources.gomemlimit value. We recommend to set gomemlimit to around 80% of limits.memory.

If you leave the default gomemlimit in place and have a higher limits.memory setting, Golang’s garbage collection might spend more CPU cycles than necessary.

New Contributors

• @thiemok made their first contribution in https://github.com/dash0hq/dash0-operator/pull/621

Full Changelog: https://github.com/dash0hq/dash0-operator/compare/0.91.0...0.92.0