Hello folks! I’m facing an issue deploying the dat...
# all-things-deployment
c
Hello folks! I’m facing an issue deploying the datahub-helm on k8s with my own elasticsearch (using ECK operator), instead of the elastic that the prerequisites helm installs by default. Looks like datahub-gms is having troubles connecting to the elasticsearch I’ve provided, (but it’s strange that the
elasticsearchSetupJob
works perfectly fine). Does anyone knows how to solve this? It seems to be a security/auth issue, so I don’t know which channel is the best one to ask this. Issue has been reported on the datahub-helm repo (https://github.com/acryldata/datahub-helm/issues/17)
e
Hey @creamy-smartphone-10810, we will look into this issue. Thanks for flagging it
👍 1
e
Could you try to ssh into the pod and try curling the endpoint mentioned in the error message? <<host>>/<<URI>>
c
hey @early-lamp-41924 yes sure
From inside the `datahub-gms`pod, if I curl like
<host>/<URI>
without any
auth
on the `<host>`side, I got the same auth 401 error as expected.
A curl with
<http://username:pwd@host/>
is working (200 answer)
And with the URI that appears on the error it gives me:
Copy code
* Connected to data-elasticsearch-es-http.elastic-data (172.20.154.92) port 9200 (#0)
* Server auth using Basic with user 'elastic'
> GET /graph_service_v1?ignore_throttled=false HTTP/1.1
> Host: data-elasticsearch-es-http.elastic-data:9200
> Authorization: Basic ZWxhc3RpYzoyNTdYYUtFODJCNmNiWDgyMXVZaWpWNVc=
> User-Agent: curl/7.79.1
> Accept: */*
> 
* Mark bundle as not supporting multiuse
< HTTP/1.1 404 Not Found
< X-elastic-product: Elasticsearch
< content-type: application/json; charset=UTF-8
< content-length: 425
< 
* Connection #0 to host data-elasticsearch-es-http.elastic-data left intact
{"error":{"root_cause":[{"type":"index_not_found_exception","reason":"no such index [graph_service_v1]","resource.type":"index_or_alias","resource.id":"graph_service_v1","index_uuid":"_na_","index":"graph_service_v1"}],"type":"index_not_found_exception","reason":"no such index [graph_service_v1]","resource.type":"index_or_alias","resource.id":"graph_service_v1","index_uuid":"_na_","index":"graph_service_v1"},"status":404}
hey @early-lamp-41924 @echoing-airport-49548 any news on this? (i’ve placed the prerequisits elastic to continue working, but I would like to use my custom elastic in the future and avoid the prerequisits one)
e
Hey. what is the elasticsearch version of the es container?
also when you tested the username and password, did you try using the env variables ? instead of copying the string directly
c
hey @early-lamp-41924, we are using version 7.15.1. About the variables, I’ve used a k8s secret for de pwd, and string for username, as it appears on documentation, let me test it with env vars and I come back to you asap.