Closed miguelsorianod closed 3 years ago
With the current implementation the OpenTracing configuration is being provided with a Secret
but in the official APIcast product documentation I see a ConfigMap
is used. Maybe in this case a Secret
is not needed and we should use a ConfigMap
instead?
Ready for a first review @eguzki before I proceed to do some verifications
@eguzki I think this should be ready
This exposes OpenTracing functionality provided by APIcast into the APIcast operator.
Design
A new
spec.openTracing
section has been added in theAPIcast
CR.An example:
openTracing
section are optionalenabled
flag is not specified, it defaults tofalse
tracingLibrary
flag is not specified, it defaults tojaeger
tracingConfigRef
flag is not specified, it defaults to a default tracing configuration specific to the settracingLirary
. This default tracing configuration is provided in the APIcast image itselfThe configuration is mounted into the APIcast pod by looking at a
config
key in the provided secret name and mounted in/opt/app-root/src/tracing-configs/tracing-config-<tracing_library_name>-<secret_name>
, for example inopt/app-root/src/tracing-configs/tracing-config-jaeger-mysecretname
Pending: