Unable to see operators after install/deploy the OML by following the installation guide

[camilamacedo86]

WHAT:

Unable to see operators after install/deploy the OML by following the installation guide
Ref: https://github.com/operator-framework/operator-lifecycle-manager/blob/master/Documentation/install/install.md

What was my expectation?

After following it I would expect to have some default operators installed as an example. Following the OCP doc.

What is the current behaviour?

Following some observations:

• The installation guide does not make clear for who is getting started with it when and for what the user should do "Building deployment resources for any cluster".
• The explanation of "Subscribe to a Package and Channel" is not clear for who is getting started with it. Why should someone do it? What are the steps exactly to do it?

[ecordell]

OLM comes installed by default in openshift clusters - but I'll leave this open to track the deficiencies in our docs.

[ecordell]

If you install with the instructions here: https://github.com/operator-framework/operator-lifecycle-manager/releases/tag/0.10.0

You should see the community operators from operatorhub by default. Or, if you get OLM by default with an openshift cluster, you should see a number of operators available for install via the marketplace.

If you can replicate this, please re-open, but I believe that you always see some operators in kubernetes and openshift now.