Skip to content

Commit 938db74

Browse files
committed
Clarify install mode docs
1 parent bcb3d07 commit 938db74

1 file changed

Lines changed: 2 additions & 1 deletion

File tree

docs/project/olmv1_limitations.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,8 @@ hide:
88
Currently, OLM v1 only supports installing operators packaged in [OLM v0 bundles](https://olm.operatorframework.io/docs/tasks/creating-operator-bundle/)
99
, also known as `registry+v1` bundles. Additionally, the bundled operator, or cluster extension:
1010

11-
* **must** support installation via the `AllNamespaces`, `SingleNamespace`, or `OwnNamespace` install modes.
11+
* **must** support installation via the `AllNamespaces` install mode.
12+
* Note that `AllNamespaces` is the recommended install mode. OLMv1 supports `SingleNamespace` and `OwnNamespace` modes for `registry+v1` bundles for backwards compatibility with OLMv0, but these are not recommended install modes as there is a [hard limitation](https://operator-framework.github.io/operator-controller/project/olmv1_design_decisions/#do-not-fight-kubernetes) of only one instance of a given CRD in the cluster.
1213
* **must not** declare dependencies using any of the following file-based catalog properties:
1314
* `olm.gvk.required`
1415
* `olm.package.required`

0 commit comments

Comments
 (0)