Bug 1684329

Description of problem:

Not sure if this belongs to Logging, web console or OperatorHub.   Whoever owns the YAML used as an example to create a clusterlogging CR from web console is who this should go to.

Creating a new clusterlogging CR from the web gives sample YAML to install it in the default namespace.  Since https://github.com/operator-framework/community-operators/pull/85 clusterlogging CRs should only go to the openshift-logging namespace

1. Install the cluster logging operators from the web console (Catalog->OperatorHub->Show community operators)
2. Catalog->Installed Operators->Copied->Cluster Logging
3. Create New Cluster Logging

The sample YAML is:

apiVersion: logging.openshift.io/v1alpha1
kind: ClusterLogging
metadata:
  name: instance
  namespace: default
spec:
  managementState: Managed
  logStore:
    type: elasticsearch
    elasticsearch:
      nodeCount: 3
      redundancyPolicy: SingleRedundancy
      storage:
        storageClassName: gp2
        size: 200G
  visualization:
    type: kibana
    kibana:
      replicas: 1
  curation:
    type: curator
    curator:
      schedule: 30 3 * * *
  collection:
    logs:
      type: fluentd
      fluentd: {}




Version-Release number of selected component (if applicable): 4.0.0-0.nightly-2019-02-27-213933


How reproducible: Always