0.151.0
🛑 Breaking changes 🛑
auto-instrumentation: Update default Java auto-instrumentation version from 1.33.6 to 2.27.0 (#4996)
This is a breaking change due to HTTP semantic convention changes between versions.
Existing Instrumentation CRs using a 1.x.x version will NOT be automatically upgraded.
To upgrade, manually update the image in your Instrumentation CR after reviewing the migration guide.
See #2542 for details.
💡 Enhancements 💡
-
target allocator: AddsecretNamespacesfield to PrometheusCR configuration to make the namespaces watched for secrets configurable instead of hardcoding to the collector namespace. (#4999)
Previously, the Target Allocator always watched the collector namespace for secrets used in
ServiceMonitor/PodMonitor basicAuth and other secret references. Now, the namespaces to watch
for secrets can be explicitly configured viaspec.prometheusCR.secretNamespaces.
If not configured, no namespaces are watched for secrets. -
operator: Split kubebuilder RBAC markers and restrict pod permissions to get/list/watch only (#3156)
The operator does not create, update, patch, or delete Pod objects directly;
pods are managed by Deployment, DaemonSet, and StatefulSet controllers.
Also reduced targetallocators/finalizers to only theupdateverb. -
target allocator: Introduce kustomizaton manifests for standalone deployment (#4945)
🧰 Bug fixes 🧰
auto-instrumentation: Validatespec.apacheHttpd.configPathandspec.nginx.configFilemore strictly for Instrumentations (#4925)
Values fromInstrumentation.spec.apacheHttpd.configPathandInstrumentation.spec.nginx.configFile
are now passed to init container scripts as positional arguments instead of being concatenated into
the shell command string, so they are no longer parsed by the shell. They're also restricted to usual Unix
path characters and limited to 256 characters.