In AWS environment, when jaeger runs in kubernetes than it can access OpenSearch via dedicated vpc url.
Using that URL does not require providing any credentials (if fine-grained-access is disabled).
Problem
Using jaeger chart makes it impossible to not provide name that will be passed as ES_USERNAME.
Providing that variable makes it impossible to use OpenSearch as a backend.
Proposal
Would be nice if chart allowed to not provide that value, so it does not get rendered.
I have a working solution, using jaeger-operator (not chart, raw, in-house built manifests).
In that solution, operator takes below Jaeger config:
Requirement
In AWS environment, when jaeger runs in kubernetes than it can access OpenSearch via dedicated vpc url. Using that URL does not require providing any credentials (if fine-grained-access is disabled).
Problem
Using jaeger chart makes it impossible to not provide
name
that will be passed asES_USERNAME
. Providing that variable makes it impossible to use OpenSearch as a backend.Proposal
Would be nice if chart allowed to not provide that value, so it does not get rendered.
I have a working solution, using jaeger-operator (not chart, raw, in-house built manifests). In that solution, operator takes below Jaeger config:
and turns it into following manifest
I can't achieve same config using when using jaeger chart, which results in below failures:
Open questions
No response