@salaboy okay if it is network problem but this issue is only I’m facing in operate and the same URL, I was able to configure in broker as shown below:
logs of broker:
2020-07-07 12:06:37.785 [] [main] DEBUG io.zeebe.broker.exporter - Exporter configured with ElasticsearchExporterConfiguration{url='https://xxxxxxxxxxx.xxxxxxxxxxxxxxxxx.xxxxxxxxxx.xxxxxxxxxx.xxxxxxx.ap-south-1.es.amazonaws.com:443', index=IndexConfiguration{indexPrefix='zeebe-record', createTemplate=true, command=false, event=true, rejection=false, error=true, deployment=true, incident=true, job=true, message=false, messageSubscription=false, variable=true, variableDocument=true, workflowInstance=true, workflowInstanceCreation=false, workflowInstanceSubscription=false, ignoreVariablesAbove=8191}, bulk=BulkConfiguration{delay=5, size=1000}, authentication=AuthenticationConfiguration{username='xxxxxxxxxxxx'}}
as you can see both pods are running on the same namespaces.
Correct me if I’m wrong, but If this was the network issue then the same issue broker must-have. why only operate?
Thanks in Advance!!