[jorbaum]

Adds the otel-collector to kind deployment as its commonly used in cloudfoundry already. Deployment of otel-collector is opt-in for now.

Requires cloudfoundry/cf-k8s-releases#230 (CI currently failing due to that).

I verified locally that I am able to send otlp traffic to otelCollector.exportEndpoint via:

$ docker run --detach --name opencode-otel-collector-test --publish 4318:4317 --volume "$PWD/docs/otel-collector-local-config.yaml:/etc/otel/config.yaml:ro" otel/opentelemetry-collector-k8s:0.127.0 --config=/etc/otel/config.yaml
  external_host=$(docker exec cfk8s-control-plane sh -c "ip route | awk '/default/ {print \$3; exit}'")
  cat > /private/var/folders/gl/jsptwkgj1zq1j9xjslk0014h0000gn/T/opencode/otel-external-runtime.yaml <<EOF
  otelCollector:
    enabled: true
    exporter:
      endpoint: "${external_host}:4318"
  charts:
    loggregatorAgent:
      url: /Users/myuser/Workspace/public/cloudfoundry/cf-k8s-releases/loggregator-agent/helm
  EOF
  printf 'external_endpoint=%s:4318\n' "$external_host"
  for signal in ResourceLogs ResourceMetrics; do
    count=$(docker logs --since 5m opencode-otel-collector-test 2>&1 | grep -c "$signal" || true)
    echo "$signal=$count"
  done

Unable to find image 'otel/opentelemetry-collector-k8s:0.127.0' locally
0.127.0: Pulling from otel/opentelemetry-collector-k8s
ccb850397780: Pulling fs layer
1cb5be31027a: Pulling fs layer
1cb5be31027a: Download complete
1cb5be31027a: Pull complete
ccb850397780: Download complete
ccb850397780: Pull complete
Digest: sha256:96cacfd787592737d68d239451ded1661a27cdc106e7c4413af287ca60940e1e
Status: Downloaded newer image for otel/opentelemetry-collector-k8s:0.127.0
ff9abd377266f517404278997eefb512118c23ffb5009390298257e7584b42bd
ResourceLogs=0
ResourceMetrics=32

and internal otel-collector:

❯ kubectl --context kind-cfk8s -n cf-system logs daemonset/forwarder-agent \
  -c otel-collector --all-pods=true --prefix=true --since=1m -f |
  awk '/ResourceMetrics|Metric #[0-9]+/{print; fflush()}' | head
[pod/forwarder-agent-7wwhc/otel-collector] 2026-10-20T15:21:10.451Z	info	ResourceMetrics #0
[pod/forwarder-agent-7wwhc/otel-collector] Metric #0
[pod/forwarder-agent-7wwhc/otel-collector] 2026-10-20T15:21:10.652Z	info	ResourceMetrics #0
[pod/forwarder-agent-7wwhc/otel-collector] Metric #0
[pod/forwarder-agent-7wwhc/otel-collector] Metric #1
[pod/forwarder-agent-7wwhc/otel-collector] Metric #2
[pod/forwarder-agent-7wwhc/otel-collector] Metric #3
[pod/forwarder-agent-7wwhc/otel-collector] Metric #4
[pod/forwarder-agent-7wwhc/otel-collector] 2026-10-20T15:21:10.853Z	info	ResourceMetrics #0
[pod/forwarder-agent-7wwhc/otel-collector] Metric #0

---

Drafted by an AI coding harness, carefully reviewed.

[jorbaum]

With this next try I am now using the upstream image from otel/opentelemetry-collector-contrib .

However, I also adapted the loggregator-agent release helm chart so it includes the otel-collector. This is necessary as the forwarder-agent currently only forwards to localhost.

Alternatively one could adapt the forwarder agent to send OTLP to other locations as well. However, when we think about going that route we could also add a proper cloudfoundry loggregator envelope receiver to the otel-collector as well. I consider this out of scope for now.

[jorbaum]

I verified locally that I am able to send otlp traffic to otelCollector.exportEndpoint.

Does it make sense to add a test for that?

[jorbaum]

Implemented what we had discussed in cloudfoundry/cf-k8s-releases#230 (comment) .

Also moved the otel config into dedicated template file to follow usual conventions.