Right now, if a change is made to a deployment configuration, we Kube will redeploy the pod. This is not necessarily desirable for Elasticsearch data nodes.
If we need to make a few changes, perhaps via an ansible script, ideally we'd want to have a handler collect all the "restarts" required and issue one restart, perhaps properly synchronized with all other ES cluster pods that need to be restarted.
3.7 release https://github.com/openshift/openshift-ansible/pull/6491
Tested with logging with enabled ops cluster, make changes to ES/ES-OPS dc, the ES/ES-OPS pods won't be redeployed.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.