Fix deployment in GKE Autopilot (#1071)

For some reason the metrics-addr argument was brought back into the exception rules in GKE Autopilot side for both log engine modes. For now bring the argument back to fix the failing deployment

.chloggen/fix-gke-autopilot-deployment.yaml

@@ -0,0 +1,8 @@
+# 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, networkExplorer, operator, chart, other)
+component: agent
+# A brief description of the change. Surround your text with quotes ("") if it needs to start with a backtick (`).
+note: Fix GKE Autopilot deployment
+# One or more tracking issues related to the change
+issues: [1071]

examples/distribution-gke-autopilot/rendered_manifests/daemonset.yaml

@@ -50,6 +50,7 @@ spec:
         command:
         - /otelcol
         - --config=/conf/relay.yaml
+        - --metrics-addr=0.0.0.0:8889
         ports:
         - name: jaeger-grpc
           containerPort: 14250

helm-charts/splunk-otel-collector/templates/daemonset.yaml

@@ -246,7 +246,7 @@ spec:
         {{- else }}
         - /otelcol
         - --config=/conf/relay.yaml
-        {{- if and (eq .Values.distribution "gke/autopilot") (eq .Values.logsEngine "fluentd") }}
+        {{- if eq .Values.distribution "gke/autopilot" }}
         {{- /* Temporary no-op argument required to run collector on GKE Autopilot */}}
         - --metrics-addr=0.0.0.0:8889
         {{- end }}