-
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
[Bug]:"Failed to init storage factory","error":"failed to create primary Elasticsearch client: health check timeout: no Elasticsearch node available" #443
Comments
@navin-rai is your issue similar to this one: #441 by any chance ? |
I tried the solution given in PR, but it didn't work. |
@navin-rai did you enable fine-grained-access on OpenSearch domain? If yes, then proper credentials must be provided, if not, then you can't pass username nor password as environment variables. |
@klubi , Hi, So here is the thing what I am trying to do, I have AWS ES created, My jaeger instance is not on AWS it is on prem. The solution which you provided gives me below manifest for collector-deployment(similar for query-deployment) Source: jaeger/templates/collector-deploy.yamlapiVersion: apps/v1 |
@klubi I am not sure, is there any possibility to use AWS Secret key & Access key ? |
No, that's a completely different mechanism. - name: ES_USERNAME
value: elastic
- name: ES_PASSWORD
valueFrom:
secretKeyRef:
name: jaeger-elasticsearch also, you'd have to add below to your cmdlineParams:
es.tls.enabled: true
es.tls.skip-host-verify: true |
What happened?
I am using AWS Elasticsearch and trying to use it in jaeger, I have set the endpoints as per documentation, I am using latest version of jaeger helm chart apiVersion: v2, appVersion: 1.39.0, below is the config I am using for elasticsearch
elasticsearch:
scheme: https
host: search-*********************.us-east-1.es.amazonaws.com
port: 443
user: elastic
usePassword: true
password: *********
Steps to reproduce
Add AWS ES endpoints
helm install jaeger
Expected behavior
Jaeger Collector and Jaeger Query should deploy properly on Kubernetes.
Relevant log output
Screenshot
No response
Additional context
No response
Jaeger backend version
No response
SDK
No response
Pipeline
No response
Stogage backend
AWS Elasticsearch
Operating system
No response
Deployment model
No response
Deployment configs
No response
The text was updated successfully, but these errors were encountered: