Description of problem:
If you don't want ops stack, the route and service still get created (even if you don't mention the URL's and even when enable-ops-cluster=false was passed in the config map. ).
So if you want ops stack, you need to do enable-ops=true. But, enable-ops=false doesn't help if I don't want the ops' cluster.
In all, when I don't specify the kibana-ops domains, service + route still get created (but to example.com) even when enable-ops-cluster=false was passed in the config map.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.Don't add the KIBANA_OPS_HOSTNAME
2.Pass --from-literal enable-ops-cluster=false in the "oc create configmap logging-deployer "
3.Start the deployer
This has been corrected in the 3.5 release with the move to ansible. Closing as it is a duplicate of the referenced issue and we are unlikely to fix in the 3.2 code stream
*** This bug has been marked as a duplicate of bug 1419987 ***
Hi, apologies for opening a closed bug, but while the bug is mistakenly marked as 3.2, in the description it is 3.4 and the bug is attached to an urgent (sev1) case. Is there possibility of backport to 3.4 from 3.5?
@Miheer please clarify based on #4