📖 Clarify install mode docs

[oceanc80]

Description

Clarify install mode docs to emphasize the design decision to not fight kubernetes.

Reviewer Checklist

• API Go Documentation
• Tests: Unit Tests (and E2E Tests, if appropriate)
• Comprehensive Commit Messages
• Links to related GitHub Issue(s)

[netlify]

✅ Deploy Preview for olmv1 ready!

Name	Link
🔨 Latest commit	80eb230
🔍 Latest deploy log	https://app.netlify.com/projects/olmv1/deploys/695d8f5cd02b1900076d07aa
😎 Deploy Preview	https://deploy-preview-2430--olmv1.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[Copilot]

Pull request overview

This PR enhances the OLM v1 documentation by clarifying the install mode requirements and recommendations. The change emphasizes that AllNamespaces is the preferred install mode while explaining that SingleNamespace and OwnNamespace modes are only supported for backwards compatibility with OLM v0, with a reference to the design decision about not fighting Kubernetes and its limitation of one CRD instance per cluster.

Key Changes:

• Restructured the install mode requirement to emphasize AllNamespaces as the recommended mode
• Added explanatory note about backwards compatibility support for other install modes and their limitations

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

The term "OLMv1" should be consistently written as "OLM v1" (with a space) to match the terminology used throughout the rest of the document. The same applies to "OLMv0" which should be "OLM v0".

Suggested change

* 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.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 69.61%. Comparing base (bcb3d07) to head (80eb230).
⚠️ Report is 2 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #2430      +/-   ##
==========================================
- Coverage   73.05%   69.61%   -3.45%     
==========================================
  Files         100      100              
  Lines        7641     7641              
==========================================
- Hits         5582     5319     -263     
- Misses       1623     1888     +265     
+ Partials      436      434       -2     

Flag	Coverage Δ
e2e	46.76% <ø> (-0.09%)	⬇️
experimental-e2e	13.68% <ø> (-35.07%)	⬇️
unit	57.11% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[rashmigottipati]

/lgtm

[pedjak]

/approve

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: camilamacedo86, pedjak, rashmigottipati

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• docs/OWNERS [camilamacedo86,pedjak]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[pedjak]

/override codecov/project

[openshift-ci]

@pedjak: Overrode contexts on behalf of pedjak: codecov/project

Details

In response to this:

/override codecov/project

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.