When using Elasticsearch with SMCP the communication from the operator to the cluster is not allowed. Due to this different issues arise.

• An error message is shown like this:

• {"_ts":"2023-06-30T08:58:01.094765376Z","_level":"0","_component":"elasticsearch-operator_controllers_Elasticsearch","_message":"Unable to clear transient shard allocation","_error":{"cause":{"Op":"Put","URL":"https://elasticsearch.istio-system.svc:9200/_cluster/settings","Err":{"Op":"dial","Net":"tcp","Source":null,"Addr":{"IP":"172.30.116.74","Port":9200,"Zone":""},"Err":{}}},"cluster":"elasticsearch","msg":"failed to clear shard allocation","namespace":"istio-system","response":""},"cluster":"elasticsearch","namespace":"istio-system"}
  {"_ts":"2023-06-30T08:59:31.097607092Z","_level":"0","_component":"elasticsearch-operator_controllers_Elasticsearch","_message":"Unable to check if threshold is enabled","cluster":"elasticsearch","error":{"Op":"Get","URL":"https://elasticsearch.istio-system.svc:9200/_cluster/settings?include_defaults=true","Err":{"Op":"dial","Net":"tcp","Source":null,"Addr":{"IP":"172.30.116.74","Port":9200,"Zone":""},"Err":{}}},"namespace":"istio-system" 

• Pods to not show up as upgraded although they are updated and restarted but the operator is unable to recognise their state

We expect an appropriate NetworkPolicy to be created by SMCP when using 

manageNetworkPolicy: true 

.