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:
schedule: 30 3 * * *
Version-Release number of selected component (if applicable): 4.0.0-0.nightly-2019-02-27-213933
How reproducible: Always
Updated example to include 'openshift-logging' for the namespace.
Not fixed in 4.0.0-0.nightly-2019-03-06-074438 . Do we need something to happen upstream? Moving back to POST for now.
Fixed here . I was able to use the latest installer and the example though there seems to be some issue creating the clusterlogging instance via the UI
Verified in 4.0.0-0.nightly-2019-03-13-233958
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.