[target allocator] Update version to v0.132.0 (#2019)

* [target allocator] Update version to v0.132.0

* update example

* Update .chloggen/upgradetargetallocator.yaml

* Update .chloggen/upgradetargetallocator.yaml

* binary search for last working version

* binary search: v0.118.0 worked, now testing v0.126.0

* binary search: v0.126.0 didn't work, trying v0.122.0

* binary search: v0.122.0 didn't work, trying v0.120.0

* binary search: v0.120.0 worked, trying v0.121.0

* set collectorNotReadyGracePeriod

* set collector namespace by default

* add logs from pod not ready to test output

* fix syntax error

* attempt latest target allocator version again

to see if conn refused error in collector agent goes away

* Remove debug logging

* update changelog

* Use {{ .Release.Namespace }} in template to set default value

* Changes requested by Jina

- Leave value empty in values.yaml with comment
- Allow filling from helper template or values.yaml

* update chlog as requested by jinja2

Author: crobert-1

.chloggen/upgradetargetallocator.yaml

@@ -0,0 +1,14 @@
+# 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: Target Allocator
+# A brief description of the change. Surround your text with quotes ("") if it needs to start with a backtick (`).
+note: Update version to `v0.132.0`
+# One or more tracking issues related to the change
+issues: [2019]
+# (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: |
+  Please review the config `targetAllocator.config.collector_namespace`
+  introduced in this version which is set to the release namespace by default.

examples/with-target-allocator/rendered_manifests/targetAllocator-configmap.yaml

@@ -18,6 +18,7 @@ metadata:
 data:
   targetallocator.yaml: |
     allocation_strategy: per-node
+    collector_namespace: default
     collector_selector:
       matchlabels:
         component: otel-collector-agent

examples/with-target-allocator/rendered_manifests/targetAllocator-deployment.yaml

@@ -20,7 +20,7 @@ spec:
       serviceAccountName: default-splunk-otel-collector-ta
       containers:
         - name: targetallocator
-          image: ghcr.io/open-telemetry/opentelemetry-operator/target-allocator:v0.105.0
+          image: ghcr.io/open-telemetry/opentelemetry-operator/target-allocator:v0.132.0
           ports:
             - containerPort: 8080
               name: http-port

helm-charts/splunk-otel-collector/templates/targetAllocator-configmap.yaml

@@ -12,5 +12,9 @@ metadata:
     heritage: {{ .Release.Service }}
 data:
   targetallocator.yaml: |
-    {{- .Values.targetAllocator.config | toYaml | nindent 4 }}
+    {{- $config := .Values.targetAllocator.config }}
+    {{- if not $config.collector_namespace }}
+    {{- $_ := set $config "collector_namespace" (include "splunk-otel-collector.namespace" .) }}
+    {{- end }}
+    {{- $config | toYaml | nindent 4 }}
 {{- end }}

helm-charts/splunk-otel-collector/values.yaml

@@ -1379,7 +1379,7 @@ certmanager:
 
 targetAllocator:
   enabled: false
-  image: ghcr.io/open-telemetry/opentelemetry-operator/target-allocator:v0.105.0
+  image: ghcr.io/open-telemetry/opentelemetry-operator/target-allocator:v0.132.0
   serviceAccount:
     # Specifies whether a ServiceAccount should be created
     create: true
@@ -1391,6 +1391,8 @@ targetAllocator:
     annotations: {}
   config:
     allocation_strategy: per-node
+    # Optional: Namespace where the collector pods are running. Defaults to the release namespace,
+    collector_namespace: ""
     collector_selector:
       matchlabels:
         component: otel-collector-agent