Braunson
Braunson
@ReToCode that's an implementation detail. It is unnecessary in the fact that this domain mapping could be configured in such a way that it doesn't need to go through the...
Thanks @skonto I'm not familiar with Knative internals but I don't see why this rewrite can't happen on the ingress gateway alone. In fact this already happens when rewriting external...
Pretty neat idea
@WYGIN you could already create your own lifecycle binaries pretty sure. You just had to provide them in a tar if creating your own builder. The pack CLI during build...
Also interested in #2 in particular. Currently there is no way to identify a traced application's `environment` which makes it difficult to use in workplaces that have dev, staging, prod,...
@hanxiaop I'd like to know what perspective that is from. This is an ingress gateway yet the spans are labelled as egress. Using opentelemetry with Tempo
I agree @conradhanson however in my example the upstream is in the service mesh and has a sidecar. What you end up seeing is a root span of egress from...
This remains an issue.
Could this issue be revisited? Since Prometheus itself adds the headers for accepting OpenMetrics format, it should be possible in Promregator to add these headers and expose the results on...
It would be great if Promregator could at least, as a mitigation, pass through the `Accept` header that Prometheus sends. This would insure the upstream server (Spring in our case)...