Description of problem:

I want to add one data node in the logging cluster.  I added one item in the CRD elasticsearch.  As this item was added prior the existing one [1].  The elasticsearch operator create new deployment for all ES nodes[2]. 

I don't realized the nodes are designed as json array until I observed this.  the elasticsearch deployment name rely on the sequence in the array.  I raise this issue to discuss if we imporve the way to deploy elasticsearch. For example: add a mandatory name for each type of node item [3].

[1]
  nodes:
  - nodeCount: 1
    roles:
    - data
  - nodeCount: 3
    roles:
    - client
    - data
    - master
[2]
deployment.extensions/elasticsearch-clientdatamaster-0-1
deployment.extensions/elasticsearch-clientdatamaster-0-2
deployment.extensions/elasticsearch-clientdatamaster-0-3
deployment.extensions/elasticsearch-clientdatamaster-1-1
deployment.extensions/elasticsearch-clientdatamaster-1-2
deployment.extensions/elasticsearch-clientdatamaster-1-3
deployment.extensions/elasticsearch-data-0-1


[3]
  nodes:
  - nodeCount: 1
    roles:
    - data
    name: all-in-one
  - nodeCount: 3
    roles:
    - client
    - data
    - master
    name: data

Version-Release number of selected component (if applicable):
v4.x

How reproducible:
always

Steps to Reproduce:
1. Deploy clusterlogging via clusterlogging operators
2. Create logging CRD
   oc create -f https://raw.githubusercontent.com/openshift-qe/v3-testfiles/master/logging/clusterlogging/storageclass_name.yaml
3. there are three ES deployment

deployment.extensions/elasticsearch-clientdatamaster-0-1
deployment.extensions/elasticsearch-clientdatamaster-0-2
deployment.extensions/elasticsearch-clientdatamaster-0-3
4. Disable the clusterlogging operators
   set replicas=0 or  managementState=Unmanaged
5. Add one data node as following 
  nodes:
  - nodeCount: 1
    roles:
    - data
  - nodeCount: 3
    roles:
    - client
    - data
    - master

6.check the deployment
  oc get deployment

Actual results:
The old resource wasn't deleted, the new resource are created.

deployment.extensions/elasticsearch-clientdatamaster-0-1
deployment.extensions/elasticsearch-clientdatamaster-0-2
deployment.extensions/elasticsearch-clientdatamaster-0-3
deployment.extensions/elasticsearch-clientdatamaster-1-1
deployment.extensions/elasticsearch-clientdatamaster-1-2
deployment.extensions/elasticsearch-clientdatamaster-1-3
deployment.extensions/elasticsearch-data-0-1

oc get pvc -o name
NAME                                              
persistentvolumeclaim/elasticsearch-elasticsearch-clientdatamaster-0-1 
persistentvolumeclaim/elasticsearch-elasticsearch-clientdatamaster-0-2
persistentvolumeclaim/elasticsearch-elasticsearch-clientdatamaster-0-3
persistentvolumeclaim/elasticsearch-elasticsearch-clientdatamaster-1-1
persistentvolumeclaim/elasticsearch-elasticsearch-clientdatamaster-1-2
persistentvolumeclaim/elasticsearch-elasticsearch-clientdatamaster-1-3
persistentvolumeclaim/elasticsearch-elasticsearch-data-0-1

Expected results:
Only one data node deployment are added.

deployment.extensions/elasticsearch-clientdatamaster-0-1
deployment.extensions/elasticsearch-clientdatamaster-0-2
deployment.extensions/elasticsearch-clientdatamaster-0-3
deployment.extensions/elasticsearch-data-0-1