Retry indefinitely on filelog receiver side for noDropLogsPipeline fg

Author: dmitryax

.chloggen/retry-on-filelog-receiver.yaml

@@ -0,0 +1,12 @@
+# 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: agent
+# A brief description of the change. Surround your text with quotes ("") if it needs to start with a backtick (`).
+note: Retry indefinitely on filelog receiver if noDropLogsPipeline feature gate is enabled.
+# One or more tracking issues related to the change
+issues: [1410]
+# (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:

helm-charts/splunk-otel-collector/templates/config/_otel-agent.tpl

@@ -290,6 +290,9 @@ receivers:
     storage: file_storage
     retry_on_failure:
       enabled: true
+      {{- if .Values.featureGates.noDropLogsPipeline }}
+      max_elapsed_time: 0s
+      {{- end }}
     operators:
       {{- if not .Values.logsCollection.containers.containerRuntime }}
       - type: router