High-churn CI/CD environments on OpenShift Pipelines create observability and compliance challenges because ephemeral pods take their logs with them when they terminate. This guide shows how to deploy the Red Hat build of OpenTelemetry Collector as a DaemonSet to capture, enrich, and route Tekton pipeline logs to both local OpenShift logging (LokiStack) for fast developer troubleshooting and Splunk-HEC for long-term compliance storage. The setup includes enriching raw logs with Kubernetes and Tekton metadata (pipeline names, run UIDs, annotations), configuring RBAC and SCCs, deploying a Splunk-HEC instance as a proof-of-concept backend, and wiring OpenShift Pipelines results to retrieve archived logs from Splunk even after pods are deleted. Full YAML manifests are provided for the OpenTelemetryCollector, ConfigMaps, ClusterRoles, and TektonConfig CR adjustments.
