Open denniskniep opened 5 months ago
my preference would be to keep CRD structured rather then a flat list of parameters, similar to other options:
tracing:
datadog:
address: xxxxxxx
or
tracing:
jaeger:
collectorEndpoint: xxxx
and
imagine in future we would have OTEL export for example that may have a whole bunch of parameters and it would be nice to group them somewhere under
tracing:
otel:
this spec is used to auto-generate reference documentation with topmost level keys becoming sections: https://www.pomerium.com/docs/deploying/k8s/reference
Summary
Implements the tracing configs in the Pomerium CRD
Checklist
improvement
/bug
/ etc)