-
Story
-
Resolution: Unresolved
-
Undefined
-
None
-
None
-
None
-
False
-
None
-
False
-
-
- Users (who have access to OLM v1’s user facing ‘ClusterExtension’ API) using a ServiceAccount with sufficient permissions can install a k8s extension/operator with a desired target version or the latest version within a specific version range (from the associated channel) to get the latest security fixes.
- Users can see the recommended installation namespace if provided by the package authors for installation.
- Users get notified through error messages from the OLM API whenever two conflicting k8s extensions/operators (will be) owning the same API objects, i.e., no conflicting ownership, after triggering the installation.
- During the installation, users can see the installation progress reported from the ‘ClusterExtension’ API object.
[CONSOLE-4106] [OLM v1] Install page
Samuel Padgett
added a comment - Stale issues rot after 30d of inactivity.
Mark the issue as fresh by removing the `lifecycle-rotten` label.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by adding the `lifecycle-frozen` label.
If this issue is safe to close now please do so.
Samuel Padgett
added a comment - Stale issues rot after 30d of inactivity.
Mark the issue as fresh by removing the `lifecycle-rotten` label.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by adding the `lifecycle-frozen` label.
If this issue is safe to close now please do so. Samuel Padgett
added a comment - Issues go stale after 90d of inactivity.
Mark the issue as fresh by removing the `lifecycle-stale` label.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by adding the `lifecycle-frozen` label.
If this issue is safe to close now please do so.
Samuel Padgett
added a comment - Issues go stale after 90d of inactivity.
Mark the issue as fresh by removing the `lifecycle-stale` label.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by adding the `lifecycle-frozen` label.
If this issue is safe to close now please do so. 
Rotten issues close after 30d of inactivity.
You may reopen the issue by moving it back to TODO state and removing the `lifecycle-rotten` label. Exclude this issue from closing again by adding the `lifecycle-frozen` label.