🛑 Breaking changes 🛑
-
target allocator: Use standard K8s label selectors for collectors in target allocator config (#2422)
This is a breaking change only for users of standalone target allocator. Operator users are unaffected.
The operator is still compatible with previous target allocator versions, and will be for the next 3 releases. -
target allocator: Use container securityContext for target allocator (#2490)
This is really a bug fix, as the current behaviour is not intended. We've marked it as breaking in case anyone started depending on it.
💡 Enhancements 💡
operator: Automate the creation of the permissions needed by the resourcedetection processor (#2393)operator: Automate the creation of the permissions needed by the k8sattributes processor (#2395)target allocator: Change default allocation and filtering strategy (#2477)operator: Introduce common fields to the v1alpha2 types that can be reused for any CRDs. (#901)target allocator: Use Pod securityContext for target allocator (#2495)
Bring back PodSecurityContext as it was removed in the previous changes.bridge: Sets pods in the component health map (#2489)
this change adds a requirement for a new permission for the bridge to list and get pods.