You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: staging/operator-lifecycle-manager/README.md
+20-1Lines changed: 20 additions & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -44,7 +44,9 @@ Install OLM on a Kubernetes or OpenShift cluster by following the [installation
44
44
45
45
For a complete end-to-end example of how OLM fits into the Operator Framework, see the [Operator Framework Getting Started Guide](https://github.com/operator-framework/getting-started).
46
46
47
-
### User Interface
47
+
**NOTE:** OLM is installed by default in OpenShift 4.0 and above.
48
+
49
+
## User Interface (Running the console Locally)
48
50
49
51
Use the OpenShift admin console (compatible with upstream Kubernetes) to interact with and visualize the resources managed by OLM. Create subscriptions, approve install plans, identify Operator-managed resources, and more.
50
52
@@ -56,6 +58,18 @@ $ make run-console-local
56
58
57
59
Then visit `http://localhost:9000` to view the console.
58
60
61
+
## End-to-end example
62
+
63
+
For a complete end-to-end example of how OLM fits into the Operator Framework, see the [Operator Framework Getting Started Guide](https://github.com/operator-framework/getting-started). Also, see [Getting Started on OperatorHub.io](https://operatorhub.io/getting-started).
64
+
65
+
## Contributing your Operator
66
+
67
+
Have an awesome Operator you want to share? Checkout the [publishing docs](https://operatorhub.io/contribute) to learn about contributing to [OperatorHub.io](https://operatorhub.io/).
68
+
69
+
## Subscribe to a Package and Channel
70
+
71
+
Cloud Services can be installed from the catalog by subscribing to a channel in the corresponding package.
If any part of the operator-lifecycle-manager project has bugs or documentation mistakes, please let us know by [opening an issue][operator-olm-issue]. We treat bugs and mistakes very seriously and believe no issue is too small. Before creating a bug report, please check that an issue reporting the same problem does not already exist.
4
+
To make the bug report accurate and easy to understand, please try to create bug reports that are:
5
+
6
+
- Specific. Include as much details as possible: which version, what environment, what configuration, etc.
7
+
8
+
- Reproducible. Include the steps to reproduce the problem. We understand some issues might be hard to reproduce, please include the steps that might lead to the problem.
9
+
10
+
- Isolated. Please try to isolate and reproduce the bug with minimum dependencies. It would significantly slow down the speed to fix a bug if too many dependencies are involved in a bug report. Debugging external systems that rely on operator-lifecycle-manager is out of scope, but we are happy to provide guidance in the right direction or help with using operator-lifecycle-manager itself.
11
+
12
+
- Unique. Do not duplicate existing bug report.
13
+
14
+
- Scoped. One bug per report. Do not follow up with another bug inside one report.
15
+
16
+
It may be worthwhile to read [Elika Etemad’s article on filing good bug reports][filing-good-bugs] before creating a bug report.
17
+
18
+
We might ask for further information to locate a bug. A duplicated bug report will be closed.
0 commit comments