Elastic search not getting installed via helm charts for jaeger

360 views
Skip to first unread message

Saranya Nagaraj

unread,
Apr 24, 2022, 9:04:13 AM4/24/22
to Jaeger Tracing
Hi All,

I'm trying to install Jaeger via helm on GKE, 
but ELK is not getting deployed.

I'm using this custom overridden values file - https://github.com/rookie-coder-py/k8s/blob/main/values_helm.yaml#L34-L41 ,
with only the below lines change from the default one (https://github.com/jaegertracing/helm-charts/blob/main/charts/jaeger/values.yaml)
I.e enabled elastic search and updated the es_server_url. NOT USING TLS for elk,

I'm not using jaeger-operator since we need to make changes in values.yml as per our company image repo.

student_04_c67f841abb7a@cloudshell:~ (qwiklabs-gcp-04-e1dd7a7c2028)$ k get svc
NAME               TYPE           CLUSTER-IP    EXTERNAL-IP      PORT(S)                                           AGE
jaeger-agent       ClusterIP      10.60.1.135   <none>           5775/UDP,6831/UDP,6832/UDP,5778/TCP,14271/TCP     23m
jaeger-collector   LoadBalancer   10.60.6.39    34.122.239.168   14250:30836/TCP,14268:32023/TCP,14269:32220/TCP   23m
jaeger-query       LoadBalancer   10.60.1.210   35.184.72.245    80:30153/TCP,16687:30168/TCP                      23m
kubernetes         ClusterIP      10.60.0.1     <none>           443/TCP                                           32m

I get below error after deployment in jaeger-collector and jaeger-query.
Failed to init storage factory","error":"failed to create primary Elasticsearch client: health check timeout.


Can someone please guide??
Reply all
Reply to author
Forward
0 new messages