Release v0.114.0
0.114.0
💡 Enhancements 💡
-
collector: Create RBAC rules for the k8s_cluster receiver automatically. (#3427) -
collector: Create RBAC rules for the k8sobjects receiver automatically. (#3429) -
collector: Add a warning message when one created collector needs extra RBAC permissions and the service account doesn't have them. (#3432) -
target allocator: Added allocation_fallback_strategy option as fallback strategy for per-node allocation strategy, can be enabled with feature flag operator.targetallocator.fallbackstrategy (#3477)If using per-node allocation strategy, targets that are not attached to a node will not
be allocated. As the per-node strategy is required when running as a daemonset, it is
not possible to assign some targets under a daemonset deployment.
Feature flag operator.targetallocator.fallbackstrategy has been added and results in consistent-hashing
being used as the fallback allocation strategy for "per-node" only at this time. -
auto-instrumentation: updated node auto-instrumentation dependencies to the latest version (#3476)- auto-instrumentations-node to 0.53.0
- exporter-metrics-otlp-grpc to 0.55.0
- exporter-prometheus to 0.55.0
-
operator: Replace references to gcr.io/kubebuilder/kube-rbac-proxy with quay.io/brancz/kube-rbac-proxy (#3485)
🧰 Bug fixes 🧰
-
operator: Operator pod crashed if the Service Monitor for the operator metrics was created before by another operator pod. (#3446)Operator fails when the pod is restarted and the Service Monitor for operator metrics was already created by another operator pod.
To fix this, the operator now sets the owner reference on the Service Monitor to itself and checks if the Service Monitor already exists. -
auto-instrumentation: Bump base memory requirements for python and go (#3479)