Skip to content

Add otel-collector-release based on upstream helm - #493

Draft
jorbaum wants to merge 2 commits into
cloudfoundry:mainfrom
jorbaum:add-otel-collector
Draft

jorbaum wants to merge 2 commits into
cloudfoundry:mainfrom
jorbaum:add-otel-collector

Conversation

@jorbaum

@jorbaum jorbaum commented Sep 1, 2026

Copy link
Copy Markdown
Contributor

Uses upstream helm chart but our own otel distro

Requires cloudfoundry/cf-k8s-releases#230 to have an image to deploy and cloudfoundry/otel-collector-release#263 to have the health check component which is required by the upstream helm chart.

Also adds a new env var that determines if otel-collector is deployed or not.


Drafted by an AI coding harness, not yet carefully reviewed.

Comment thread helmfile.yaml.gotmpl
Comment on lines +180 to +182
image:
repository: ghcr.io/cloudfoundry/k8s/otel-collector
tag: {{ .Values.charts.otelCollector.imageTag | quote }}

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

we must simply re-use the OS image, no additional configuration is required

Comment thread versions.yaml
Comment on lines +48 to +49
# renovate: dataSource=github-releases depName=cloudfoundry/otel-collector-release
imageTag: "0.11.10"

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Uses upstream helm chart but our own otel distro
* Also configures healthcheck for otel collector
otel-collector is still experimental and should not be deployed by
default
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants