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: doc/install/install.md
+18-5Lines changed: 18 additions & 5 deletions
Original file line number
Diff line number
Diff line change
@@ -2,7 +2,7 @@
2
2
3
3
OLM deployment resources are templated so that they can be easily configured for different deployment environments.
4
4
5
-
Check out the latest [releases on github](https://github.com/operator-framework/operator-lifecycle-manager/releases) for release-specific install instructions.
OLM is installed by default in OpenShift 4.0 and above.
17
+
Check out the latest [releases on github](https://github.com/operator-framework/operator-lifecycle-manager/releases) for release-specific install instructions.
18
18
19
19
## Run locally with minikube
20
20
21
21
This command starts minikube, builds the OLM containers locally with the minikube-provided docker, and uses the local configuration in [local-values.yaml](local-values.yaml) to build localized deployment resources for OLM.
22
22
23
-
```
24
-
make run-local
23
+
```bash
24
+
# To install and run locally
25
+
$ make run-local
25
26
```
26
27
27
28
You can verify that the OLM components have been successfully deployed by running `kubectl -n local get deployments`
28
29
30
+
**NOTE** It is recommended for development purposes and will use the source locally
31
+
32
+
## OpenShift
33
+
34
+
**IMPORTANT:** OLM is installed by default in OpenShift 4.0 and above.
35
+
29
36
## Customizing OLM installation
30
37
31
38
Deployments of OLM can be stamped out with different configurations by writing a `values.yaml` file and running commands to generate resources.
0 commit comments