Description of problem:
When creating a default EFK stack some kibana-ops are still created.

Version-Release number of selected component (if applicable):
3.4.1

How reproducible:
Every time

Steps to Reproduce:
1. Deploy according to documentation
Make sure to not define any ops variables.

$ oc export configmap logging-deployer
apiVersion: v1
data:
  es-cluster-size: "1"
  es-instance-ram: 1G
  kibana-hostname: kibana.cloudapps.example.com
  public-master-url: https://openshift.example.com:8443
kind: ConfigMap
metadata:
  creationTimestamp: null
  name: logging-deployer


2.
$ oc get all | grep ops


routes/logging-kibana-ops   kibana-ops.example.com               logging-kibana-ops   <all>     reencrypt

svc/logging-es-ops           172.30.207.176   <none>        9200/TCP   50m
svc/logging-es-ops-cluster   172.30.105.134   <none>        9300/TCP   50m
svc/logging-kibana-ops       172.30.229.129   <none>        443/TCP    50m


3.

Actual results:
ops resources created

Expected results:
When a cluster admin deploys without the ops components it's reasonable to expect that no such resources should be created.


Additional info: