-
Notifications
You must be signed in to change notification settings - Fork 348
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[jaeger-v2] Add support for Elasticsearch #617
Conversation
Signed-off-by: Reddysekhar Gaduputi <[email protected]> upgrade jaeger-operator to latest 1.61.0 (jaegertracing#605) Signed-off-by: Blair Bowden <[email protected]> added all-in-one deployment and configmap for jaeger-v2 Signed-off-by: Mehul <[email protected]> lint fix Signed-off-by: Mehul <[email protected]> fixed Signed-off-by: Mehul <[email protected]> lint fix Signed-off-by: Mehul <[email protected]> lint fix Signed-off-by: Mehul <[email protected]> fixed using pre-hook Signed-off-by: Mehul <[email protected]> fixed --config flag is not been passed Signed-off-by: mehul <[email protected]> release ns for config-map.yaml Signed-off-by: mehul <[email protected]> testing ci Signed-off-by: mehul <[email protected]> testing ci Signed-off-by: mehul <[email protected]> fixed ns Signed-off-by: mehul <[email protected]> fixed ns Signed-off-by: mehul <[email protected]> fixed template Signed-off-by: mehul <[email protected]> removed sampling Signed-off-by: mehul <[email protected]> removed adaptive sampling from processors Signed-off-by: mehul <[email protected]> Revert "Jaeger v2 test2" Signed-off-by: mehul <[email protected]> attempt to create v2 chart in v1 Signed-off-by: mehul <[email protected]> enabled collector query and agent Signed-off-by: mehul <[email protected]> version bump Signed-off-by: mehul <[email protected]> testing-v2-ci Signed-off-by: mehul <[email protected]> testing-v2-ci Signed-off-by: mehul <[email protected]> added --helm-extra-set-args flag Signed-off-by: mehul <[email protected]> fixed healthcheck port-v2 Signed-off-by: mehul <[email protected]> Fix health check path Signed-off-by: Yuri Shkuro <[email protected]> minor changes Signed-off-by: mehul <[email protected]>
Signed-off-by: mehul gautam <[email protected]>
Signed-off-by: mehul <[email protected]>
…elm-charts into jaeger-v2-with-v1
Signed-off-by: mehul <[email protected]>
Signed-off-by: mehul <[email protected]>
Signed-off-by: mehul <[email protected]>
Signed-off-by: mehul <[email protected]>
Signed-off-by: mehul <[email protected]>
Signed-off-by: mehul <[email protected]>
Signed-off-by: mehul <[email protected]>
Signed-off-by: mehul <[email protected]>
Signed-off-by: mehul <[email protected]>
Signed-off-by: mehul <[email protected]>
Signed-off-by: mehul <[email protected]>
Signed-off-by: mehul gautam <[email protected]>
Signed-off-by: mehul <[email protected]>
Signed-off-by: Yuri Shkuro <[email protected]>
Signed-off-by: mehul <[email protected]>
Signed-off-by: mehul <[email protected]>
Signed-off-by: mehul <[email protected]>
Signed-off-by: mehul gautam <[email protected]>
please write complete PR title and description |
backends: | ||
some_storage: | ||
elasticsearch: | ||
index_prefix: {{- .Values.storage.elasticsearch.index_prefix | quote | indent 2 }} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't like this. Values.storage.elasticsearch.index_prefix
is a separate domain-specific configuration language that exists only in the Operator - why do we need it? The users can provide their own custom config if they want to customize these things. If we still want to allow overriding specific fields of the built-in configuration, then those overrides should be using the OTEL config syntax, e.g. Values.config.extensions.jaeger_storage...etc...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I wanted to keep the flag syntax same as jaeger-v1 so if the users wants to run it with old flag he can set it that way and helm will use es-user-conifg.yaml
for that but if the user wants to provide there own config he can use the -set-file
flag in that case we will use user-config.yaml
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The old chart had no choice but to invent a new configuration scheme since jaeger-v1 did not support configuration, only cli flags. V2 supports configuration, so using a different scheme in the operator means the user needs to learn two different schemes, jaeger config and operator config. We need to avoid it. Use new scheme only when absolutely necessary, like in provision storage instructions, but for everything that can already be expressed in otel config just use that config directly.
user-config.yaml
Outdated
@@ -0,0 +1,45 @@ | |||
service: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
should this file be called user-config.yaml
? It's ES-specific.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No, if the user provides their own config, this will be used instead of es-user-config.yaml
.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
is this file meant to be an example config?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please add comments in the header explaining the purpose of the file
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
?
Signed-off-by: mehul <[email protected]>
…elm-charts into jaeger-v2-with-v1
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
please document in the README how the user is expected to use the chart with ES, using different options such as providing params via --set
or a full config via --set-file
user-config.yaml
Outdated
@@ -0,0 +1,45 @@ | |||
service: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
is this file meant to be an example config?
Signed-off-by: mehul <[email protected]>
user-config.yaml
Outdated
@@ -0,0 +1,45 @@ | |||
service: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please add comments in the header explaining the purpose of the file
Signed-off-by: mehul <[email protected]>
Signed-off-by: mehul <[email protected]>
@@ -4,6 +4,8 @@ description: A Jaeger Helm chart for Kubernetes | |||
name: jaeger | |||
type: application | |||
version: 4.0.0 | |||
annotations: | |||
Jaegerv1Version: "1.62.0" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you elaborate why this variable is defined in annotations
instead of values.yaml
? What is the significance of having it here?
Signed-off-by: mehul <[email protected]>
Signed-off-by: mehul <[email protected]>
Signed-off-by: mehul <[email protected]>
Signed-off-by: mehul <[email protected]>
Signed-off-by: mehul <[email protected]>
Signed-off-by: mehul <[email protected]>
What this PR does
added support for elasticsearch in jaeger-v2 helm chart
Which issue this PR fixes
(optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)
format,will close that issue when PR gets merged)
Checklist
[jaeger]
or[jaeger-operator]
)