Merged
Conversation
Changed in chart 1.21.1: > Breaking Change * In order to be consistent with other projects and documentations, the default port has been changed from 3100 to 3200.
…jaeger It changed somewhere between chart 3.4.1 and 4.5.0 (massive restructure)
This allows otelcollector configs to be used by pods in any namespace and make it easier to use Secret Operator generated TLS certs so grafana can connect to datasources securely.
sbernauer
approved these changes
Apr 24, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Sibling PR to #398
Tip
Once stackabletech/stackable-cockpit#440 is released, testing of this will be far more automated.
See test procedure further below for now.
Test procedure
Drop the URL prefix for the stack in
stacks-v2.yaml(in case of local changes), then run:Then, with
values.yaml:yes overkill with anchors, but I used it with other operators too - those are removed for brevity, but the anchors seemed useful in future.
Install an operator with OTLP logs/traces:
Then create a Trino Cluster to generate some logs/traces.
kubectl apply -f - # Press CTRL-D after pasting the belowThen check that there are trino-operator logs and traces in Grafana.