Skip to content

Make downstream otlp host configurable - #734

Open
jorbaum wants to merge 2 commits into
mainfrom
configurable-otlp-host
Open

jorbaum wants to merge 2 commits into
mainfrom
configurable-otlp-host

Conversation

@jorbaum

@jorbaum jorbaum commented Oct 13, 2026

Copy link
Copy Markdown
Contributor

Make downstream otlp host configurable. Similar to https://github.com/cloudfoundry/loggregator-agent-release/pull/708/changes , but for otlp egress, not for loggregator envelope ingress.

We need this as in kind-deployment otel-collector and forwarder agent do not run on the same machine (see cloudfoundry/kind-deployment#493 ).

Type of change

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • This change requires a documentation update

Testing performed?

  • Unit tests
  • Integration tests
  • Acceptance tests

Checklist:

  • This PR is being made against the main branch, or relevant version branch
  • I have made corresponding changes to the documentation
  • I have added testing for my changes

If you have any questions, or want to get attention for a PR or issue please reach out on the #logging-and-metrics channel in the cloudfoundry slack

In K8s otel-collector and forwarder agent likely do not run on the
same machine.
@jorbaum

jorbaum commented Oct 13, 2026

Copy link
Copy Markdown
Contributor Author

Tested by deploying this in cf on kind via cloudfoundry/kind-deployment#493 and checking via an external otel-collector-outside-kind that metrics are being forwarded.

I think this is a small enough change so we do not need to verify this again on an actual foundation. However, I could test it there again as well if required.

@jorbaum
jorbaum marked this pull request as ready for review October 13, 2026 15:25
@jorbaum
jorbaum requested a review from a team as a code owner October 13, 2026 15:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Development

Successfully merging this pull request may close these issues.

1 participant