New deployment or upgrade of EFK stack fails on " Waiting for ES to be ready"

Issue

• Deploying or upgrading of EFK stack using standard playbook procedure fails with result:

FAILED - RETRYING: Waiting for ES to be ready for <logging-es-data-master-example> (1 retries left)

• In project logging, the elasticsearch container fails to get ready with event messages as follows:

LAST SEEN   FIRST SEEN   COUNT     NAME                                            KIND      SUBJECT                        TYPE      REASON      SOURCE                                   MESSAGE
1h        3h        1551      logging-es-example   Pod       spec.containers{elasticsearch}   Warning   Unhealthy   kubelet, node1.example.com   Readiness probe failed: Elasticsearch node is not ready to accept HTTP requests yet [response code: 503]

1h        3h        1551      logging-es-example   Pod       spec.containers{elasticsearch}   Warning   Unhealthy   kubelet, node2.example.com   Readiness probe failed: Elasticsearch node is not ready to accept HTTP requests yet [response code: 503]

1h        3h        1372      logging-es-lexample  Pod       spec.containers{elasticsearch}   Warning   Unhealthy   kubelet,  node3.example.com   Readiness probe failed: Elasticsearch node is not ready to accept HTTP requests yet [response code: 503]