From 938db746706ff0e7bba7b69e8f4d2fa3a4f0d3a1 Mon Sep 17 00:00:00 2001 From: Catherine Chan-Tse Date: Tue, 6 Jan 2026 16:13:07 -0500 Subject: [PATCH 1/2] Clarify install mode docs --- docs/project/olmv1_limitations.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/docs/project/olmv1_limitations.md b/docs/project/olmv1_limitations.md index 54e174b4ca..5521197f34 100644 --- a/docs/project/olmv1_limitations.md +++ b/docs/project/olmv1_limitations.md @@ -8,7 +8,8 @@ hide: Currently, OLM v1 only supports installing operators packaged in [OLM v0 bundles](https://olm.operatorframework.io/docs/tasks/creating-operator-bundle/) , also known as `registry+v1` bundles. Additionally, the bundled operator, or cluster extension: -* **must** support installation via the `AllNamespaces`, `SingleNamespace`, or `OwnNamespace` install modes. +* **must** support installation via the `AllNamespaces` install mode. + * 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. * **must not** declare dependencies using any of the following file-based catalog properties: * `olm.gvk.required` * `olm.package.required` From 80eb23041121708e43c4513ede5808d04f9fd10d Mon Sep 17 00:00:00 2001 From: Catherine Chan-Tse Date: Tue, 6 Jan 2026 17:40:20 -0500 Subject: [PATCH 2/2] Consistent terminology --- docs/project/olmv1_limitations.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/project/olmv1_limitations.md b/docs/project/olmv1_limitations.md index 5521197f34..8f0e921e34 100644 --- a/docs/project/olmv1_limitations.md +++ b/docs/project/olmv1_limitations.md @@ -9,7 +9,7 @@ Currently, OLM v1 only supports installing operators packaged in [OLM v0 bundles , also known as `registry+v1` bundles. Additionally, the bundled operator, or cluster extension: * **must** support installation via the `AllNamespaces` install mode. - * 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. + * Note that `AllNamespaces` is the recommended install mode. OLM v1 supports `SingleNamespace` and `OwnNamespace` modes for `registry+v1` bundles for backwards compatibility with OLM v0, 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. * **must not** declare dependencies using any of the following file-based catalog properties: * `olm.gvk.required` * `olm.package.required`