-
Notifications
You must be signed in to change notification settings - Fork 340
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
How to set env for Jaeger #77
Comments
We need this enhancement to enable jaeger-operator can be used in the Istio helm chart - istio/istio#9508 |
Rather than express as an environment variable, as discussed in #72 it would be good to have this defined as:
|
@objectiser it will increase the learning curve, because it is different from the original way. I do think we should provide a general way instead of adding one-by-one. What do you think? |
@clyang82 I think both approaches have their pros and cons - however I prefer the typed approach as:
|
@objectiser agree with your point - both approaches have their pros and cons. We need to consider the goal for the operator, it should not expose all of the config complexities, it should be handled by operator and provide a easy to use way. in this way, it will be used by more and more people. But the operator cannot handle all of requirements, otherwise, the operator will be very heavy. The operator should keep flexible. the operator should not introduce new configs since there always has well-known configs. Thanks. |
@jpkrohling what is your point? to provide |
I discussed with @objectiser yesterday and we'll refrain from implementing #72 for now, until we have a better understanding of the pros/cons and requirements. For this one, I think the best solution isn't via env var or typed value, but to use apiVersion: io.jaegertracing/v1alpha1
kind: Jaeger
metadata:
name: istio-tracing
spec:
strategy: production
query:
options:
query:
base-path: /jaeger
storage:
type: elasticsearch
options:
es:
server-urls: http://elasticsearch:9200 |
I'm closing this, as I think the solution from my previous comment should be sufficient. If this does not fix the problem for you, feel free to reopen this. |
@jpkrohling Thanks for your solution. It can fix my problem. |
guys, this is great and worked for me as well, thank you! We would like to expose it via ingress route /jaeger and currently we implemented the ingress object ourselves and set ingress to false inside the jaeger object: kind: ingress
...
spec:
rules:
- host: app.domain.co.uk
http:
paths:
- backend:
serviceName: jaeger-query
servicePort: 16686
path: /jaeger
---
kind: jaeger
...
spec:
ingress:
enabled: false |
@jungopro, setting the base path should have an effect in the ingress path as well: jaeger-operator/pkg/ingress/query_test.go Lines 47 to 64 in 01bb012
Are you seeing something different? |
thanks @jpkrohling. I'm using the prod strategy, not the allInOne, but I do see the change reflected. I didn't notice that before, that is helpful But, nothing is easy 😄 nginx.ingress.kubernetes.io/ingress.class: nginx
nginx.ingress.kubernetes.io/rewrite-target: /<the-base-path> I tried editing the ingress rule post-creation and add them manually but that didn't help either... I'm a bit lost to be honest. All I know is that with a stand-alone ingress rule it does work, I'm unsure if I'm missing something or simply utterly confused 😄 Thanks |
Could you open a new issue, ideally reproducible with minikube? I can take a look once we clear some other issues. |
will do. thanks. |
@jpkrohling if use the following strategy with minikube, the base path is not reflected.
output of
output of
It looks like the base path is not set at all. (ideally, correct me if i am wrong but Path should be '/jaeger' instead of *) |
@mohit-chawla could you try this instead: apiVersion: jaegertracing.io/v1
kind: Jaeger
metadata:
name: jaeger-tracing
spec:
strategy: allInOne
allInOne:
options:
query:
base-path: /jaeger |
@jpkrohling , this worked, thanks. |
I want to add base path for jaeger query (jaegertracing/jaeger-ui#258) so that the yaml file should be:
Right now, the jaeger operator cannot support set env in yaml file.
The text was updated successfully, but these errors were encountered: