Merge branch 'auto-up-obi' of github.com:MrAlias/splunk-otel-collector-chart into auto-up-obi

Author: MrAlias

.chloggen/fix-non-eks-aws-ec2-detector.yaml

@@ -1,14 +1,18 @@
 # One of 'breaking', 'deprecation', 'new_component', 'enhancement', 'bug_fix'
 change_type: enhancement
 # The name of the component, or a single word describing the area of concern, (e.g. agent, clusterReceiver, gateway, operator, chart, other)
-component: chart
+component: gateway
 # A brief description of the change. Surround your text with quotes ("") if it needs to start with a backtick (`).
-note: Add configurable resource requests and limits for the Target Allocator container
+note: Add topologySpreadConstraints support for gateway deployment
 # One or more tracking issues related to the change
-issues: [2349]
+issues: [2361]
 # (Optional) One or more lines of additional information to render under the primary note.
 # These lines will be padded with 2 spaces and then inserted directly into the document.
 # Use pipe (|) for multiline entries.
 subtext: |
-  Users can now set `targetAllocator.resources` in values.yaml to configure CPU/memory
-  requests and limits for the Target Allocator container.
+  The gateway deployment now supports `gateway.topologySpreadConstraints` to control how
+  gateway pods are distributed across topology domains (e.g., availability zones). When
+  combined with `gateway.service.trafficDistribution` (`PreferSameZone` on Kubernetes 1.35+,
+  or `PreferClose` on older versions), this enables zone-aware routing where clients prefer
+  sending traffic to gateways in the same zone. Together, these options ensure gateways are
+  evenly spread across zones while minimizing cross-AZ network traffic and costs.

.chloggen/target-allocator-resources.yaml …gateway-topology-spread-constraints.yaml.chloggen/target-allocator-resources.yaml renamed to .chloggen/gateway-topology-spread-constraints.yaml .chloggen/target-allocator-resources.yaml renamed to .chloggen/gateway-topology-spread-constraints.yaml

@@ -1,16 +1,17 @@
 # One of 'breaking', 'deprecation', 'new_component', 'enhancement', 'bug_fix'
 change_type: bug_fix
 # The name of the component, or a single word describing the area of concern, (e.g. agent, clusterReceiver, gateway, operator, chart, other)
-component: clusterReceiver
+component: agent
 # A brief description of the change. Surround your text with quotes ("") if it needs to start with a backtick (`).
-note: Set dnsPolicy to ClusterFirstWithHostNet for cluster receiver when clusterReceiver.hostNetwork is enabled
+note: Fix histogram bucket count for `kubeproxy_network_programming_duration_seconds` metric
 # One or more tracking issues related to the change
-issues: [2348]
+issues: [2328]
 # (Optional) One or more lines of additional information to render under the primary note.
 # These lines will be padded with 2 spaces and then inserted directly into the document.
 # Use pipe (|) for multiline entries.
 subtext: |
-  When clusterReceiver.hostNetwork is enabled (e.g. for EKS Auto mode), the cluster receiver
-  pod was unable to resolve in-cluster DNS names. Pods running with
-  hostNetwork fall back to the node's DNS configuration unless dnsPolicy is explicitly set
-  to ClusterFirstWithHostNet. This matches the existing daemonset behavior.
+  Splunk Observability Cloud has a limit of 32 buckets for histograms. By default this histogram
+  has more than 32 buckets, so the config will now merge buckets to meet the required limit
+  to avoid this metric being dropped entirely. This change is relevant when both the
+  `useControlPlaneMetricsHistogramData` feature gate and `agent.controlPlaneMetrics.proxy`
+  config option are both enabled.

…gen/fix-cluster-receiver-dns-policy.yaml .chloggen/handlehistogrambuckets.yaml.chloggen/fix-cluster-receiver-dns-policy.yaml renamed to .chloggen/handlehistogrambuckets.yaml .chloggen/fix-cluster-receiver-dns-policy.yaml renamed to .chloggen/handlehistogrambuckets.yaml

@@ -1,14 +1,15 @@
 # One of 'breaking', 'deprecation', 'new_component', 'enhancement', 'bug_fix'
-change_type: enhancement
+change_type: bug_fix
 # The name of the component, or a single word describing the area of concern, (e.g. agent, clusterReceiver, gateway, operator, chart, other)
 component: chart
 # A brief description of the change. Surround your text with quotes ("") if it needs to start with a backtick (`).
-note: Bump the OBI subchart to upstream opentelemetry-ebpf-instrumentation 0.6.0
+note: Add probes and scrapeconfigs RBAC permissions to Target Allocator ClusterRole
 # One or more tracking issues related to the change
-issues: [2300]
+issues: [2359]
 # (Optional) One or more lines of additional information to render under the primary note.
 # These lines will be padded with 2 spaces and then inserted directly into the document.
 # Use pipe (|) for multiline entries.
 subtext: |
-  Updates the vendored OBI dependency and rendered eBPF instrumentation example
-  manifests to the upstream 0.6.0 chart release.
+  The Target Allocator ClusterRole was missing permissions for `probes` and `scrapeconfigs`
+  resources in the `monitoring.coreos.com` API group. This caused the allocator to fail with
+  forbidden errors when attempting to list and watch these resources.