Description of problem:
When creating a default EFK stack some kibana-ops are still created.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Deploy according to documentation
Make sure to not define any ops variables.
$ oc export configmap logging-deployer
$ 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
ops resources created
When a cluster admin deploys without the ops components it's reasonable to expect that no such resources should be created.
@Eric, this is consistent with the deployer behavior since inception. With the introduction of openshift-ansible, we only create the resources we need. Do you see it worth the effort to fix for 3.4. I'm inclined to not fix given the availble resources .
*** Bug 1421021 has been marked as a duplicate of this bug. ***
Closing as we are unlikely to fix in 3.4 given the fact the resources exist does not really cause any issues. This behavior has been corrected in 3.5 with the move to Ansible.