Clarify ports condition in service template (signalfx#416)

* Clarify ports condition in service template

This PR clarifies the condition in two ways:

  * It replaces `eq true …` with `or …`, which should be easier to
    understand for most readers.

  * It moves the four disjuncts to their own lines, making it easier for
    a human to parse the condition as a whole and its subexpressions.

💡 `git show --color-words` is useful.

* Use Helm 3.5-compatible solution

* Link to specific PR comment

* Update helm-charts/splunk-otel-collector/templates/service.yaml

* Update service.yaml

* Bring back comment

* Revert "Bring back comment"

This reverts commit 38cffb2.

Co-authored-by: Dmitrii Anoshin <[email protected]>

Fix generation of service.name log attribute in istio environment (si…

…gnalfx#176)

Istio has an involved logic for generating service name for traces. So we cannot just rely on "app" pod label. This commit adds the same logic to generate service.name logs attribute as istio uses for traces. It's needed to make correlation between logs and traces work OOTB in Splunk o11y suite.

Bump splunk-otel-collector image (signalfx#174)

Bump chart version (signalfx#173)

Update Collector version to 0.28.1 (signalfx#166)

Upgrade splunk-otel-collector image (signalfx#164)

Make auto-detection of prometheus metrics disabled by default (signal…

…fx#163)

Add an additional "autodetect.prometheus" flag to enable automatic prometheus endpoint detection and make it disabled by default.

Fix logs only configuration (signalfx#161)

Don't use hostfs volume for container runtime detection, since it's needed for logs only and hostfs volume not created for logs pipeline.

Release 0.26.3 (signalfx#160)

Automatically detect container runtime and apply relevant parsing con…

…fig (signalfx#154)

This change makes transition from deprecated docker to containerd runtime not disruptive.

Otherwise, users have to change criTimeFormat property and upgrade the chart release after they upgraded k8s cluster to a new version.