Cause: Elasticsearch default value for sharing storage between ES instances was wrong
Consequence: The incorrect default value allowed an ES pod starting up (when another ES pod was shutting down, e.g. during dc redeployments) to create a new location on the PV for managing the storage volume, duplicating data, and in some instances, potentially causing data loss.
Fix: All ES pods now run with "node.max_local_storage_nodes" set to 1.
Result: The ES pods starting up/shutting down will no longer share the same storage and prevent the data duplication and/or data loss.