I am running into an interesting issue with a docker container running in kubernetes
We are running a Node application that is using the client found here https://www.npmjs.com/package/@elastic/elasticsearch version 7.6.1. Our elastic cluster version is 6.2.0.
This is an example of the error we are getting:
Failed to get Access History Summary from Elasticsearch. StackTrace: ConnectionError: connect EADDRNOTAVAIL 10.100.30.1:9200 - Local (172.16.35.171:0) at onResponse (/opt/gemalto/src/node_modules/@elastic/elasticsearch/lib/Transport.js:214:13) at ClientRequest.<anonymous> (/opt/gemalto/src/node_modules/@elastic/elasticsearch/lib/Connection.js:98:9) at ClientRequest.emit (events.js:311:20) at TLSSocket.socketErrorListener (_http_client.js:426:9) at TLSSocket.emit (events.js:311:20) at emitErrorNT (internal/streams/destroy.js:92:8) at emitErrorAndCloseNT (internal/streams/destroy.js:60:3) at processTicksAndRejections (internal/process/task_queues.js:84:21)
What is weird is that this pod was running just fine and then started having this issue. A restart of the deployment fixed the issue.
Any ideas what might be causing the problem?