Elasticsearch hostname is not resolved by fluend and kibana when internal domain is used

Solution Verified - Updated -

Issue

  • Fluentd and kibana pods are unable to resolve elasticsearch hostname.
  • Fluentd pod reports below logs:

    2021-03-28T04:25:16.095607233Z 2021-03-28 04:25:16 +0000 [warn]: [default] failed to flush the buffer. retry_time=3 next_retry_seconds=2021-03-28 04:25:20 +0000 chunk="5be8a1fd530465ad135bed371a2c729a" error_class=Fluent::Plugin::ElasticsearchOutput::RecoverableRequestFailure error="could not push logs to Elasticsearch cluster ({:host=>\"elasticsearch.openshift-logging.svc.cluster.local\", :port=>9200, :scheme=>\"https\"}): Couldn't resolve host name"
    
  • Kibana pod reports below logs:

    2021-03-28T04:24:50.963666757Z {"type":"log","@timestamp":"2021-03-28T04:24:50Z","tags": ["warning","elasticsearch","admin"],"pid":117,"message":"No living connections"} 
    2021-03-28T04:24:53.469808289Z {"type":"log","@timestamp":"2021-03-28T04:24:53Z","tags": "warning","elasticsearch","admin"],"pid":117,"message":"Unable to revive connection: https://elasticsearch.openshift-logging.svc.cluster.local:9200/"}
    

Environment

  • Red Hat OpenShift Container Platform (RHOCP)
    • 4.6
    • 4.7
  • Red Hat OpenShift Logging
    • 5.0.0

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content