OPRUN-3767: Add OLMv1 Single/OwnNamespace EP #1774
Conversation
openshift-ci
bot
added
the
do-not-merge/work-in-progress
|
Skipping CI for Draft Pull Request. |
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
| OLMv0 offered multiple install modes (AllNamespaces, MultiNamespace, SingleNamspace, OwnNamespace). These install modes are an implementation detail of OLMv0 support for multi-tenancy, to allow the installation of the same operator multiple times on the same cluster. | ||
|
|
||
| Because OLMv0 multi-tenancy features have been the source of a wide variety of problems, OLMv1 made a deliberate decision to not implement the same mechanisms. | ||
| Today OLMv1 only supports operator bundles who chose the AllNamespaces installMode. |
There was a problem hiding this comment.
| Today OLMv1 only supports operator bundles who chose the AllNamespaces installMode. | |
| Today OLMv1 only supports operator bundles who support the AllNamespaces installMode. |
| However, customers are looking for SingleNamespace and OwnNamespace installmode. Here are some use cases for this: | ||
|
|
||
| - Due to isolation concerns, some operators prefer to not support AllNamespaces installMode | ||
| - Customers have existing OLM V0 operators which are support singleNamespace and OwnNamespace installmode |
There was a problem hiding this comment.
Having trouble parsing this one. Having a stab at it:
| - Customers have existing OLM V0 operators which are support singleNamespace and OwnNamespace installmode | |
| - Customers have existing OLM V0 operators which only support SingleNamespace and OwnNamespace installmode |
| - Due to isolation concerns, some operators prefer to not support AllNamespaces installMode | ||
| - Customers have existing OLM V0 operators which are support singleNamespace and OwnNamespace installmode | ||
|
|
||
| This Brief outlines how OLMv1 can be compatible with OLMv0 Single- and OwnNamespace installModes, without re-introducing problematic multi-tenancy features. |
There was a problem hiding this comment.
| This Brief outlines how OLMv1 can be compatible with OLMv0 Single- and OwnNamespace installModes, without re-introducing problematic multi-tenancy features. | |
| This enhancement proposal outlines how OLMv1 can be compatible with OLMv0 Single- and OwnNamespace installModes, without re-introducing problematic multi-tenancy features. |
| - User can configure registry+v1 bundle installation mode through the ClusterExtension API | ||
| - API reviewed and approved by API review Gods | ||
| - User can install a registry+v1 bundle in SingleNamespace mode | ||
| - User can install a registry+v1 bundle in OwnNamespace mode | ||
| - Additional testing ensures generated content is inline with what v0 produces (i.e. user’s expectations won’t be violated), and we are confident future changes to the RukPak package won’t cause behavioral regressions |
There was a problem hiding this comment.
| - User can configure registry+v1 bundle installation mode through the ClusterExtension API | |
| - API reviewed and approved by API review Gods | |
| - User can install a registry+v1 bundle in SingleNamespace mode | |
| - User can install a registry+v1 bundle in OwnNamespace mode | |
| - Additional testing ensures generated content is inline with what v0 produces (i.e. user’s expectations won’t be violated), and we are confident future changes to the RukPak package won’t cause behavioral regressions | |
| - User can configure their desired registry+v1 bundle installation mode through the ClusterExtension API | |
| - User can install a registry+v1 bundle in SingleNamespace mode - if the bundle supports it | |
| - User can install a registry+v1 bundle in OwnNamespace mode - if the bundle supports it | |
| - Additional testing ensures generated content is inline with what v0 produces (i.e. user’s expectations won’t be violated), and we are confident future changes to the registry+v1 rendering package won’t cause behavioral regressions |
|
/retitle OPRUN-3767: Add OLMv1 Single/OwnNamespace EP |
openshift-ci
bot
changed the title
openshift-ci-robot
added
the
jira/valid-reference
|
@thetechnick: This pull request references OPRUN-3767 which is a valid jira issue. In response to this: 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 openshift-eng/jira-lifecycle-plugin repository. |
|
Inactive enhancement proposals go stale after 28d of inactivity. See https://github.com/openshift/enhancements#life-cycle for details. Mark the proposal as fresh by commenting If this proposal is safe to close now please do so with /lifecycle stale |
openshift-ci
bot
added
the
lifecycle/stale
No description provided.