Loading...

XML

Word

Printable

Type: Epic
Resolution: Done-Errata
Priority: Undefined
Fix Version/s: None
Affects Version/s: None
Component/s: None
Labels:
- groomed

Epic Name:
disconnected obo
Blocked:
False
Blocked Reason:
None
Ready:
False
Color Status:
Not Selected
Docs QE Status:
NEW
Epic Status:
To Do
QE Status:
NEW
Hierarchy Progress Bar:

0% To Do, 0% In Progress, 100% Done
Target Version:

openshift-4.16

RICE Score:
0

SFDC Cases Links:
SFDC Cases Counter:
SFDC Cases Open:

Intelligence Requested:
Market:

Operator-sdk has a feature and tooling to support installing an operator in disconnected environments.

For OBO to support this, the operator needs to be aware of all images that are deployed by second level operators (at the moment only prometheus-operator). If the CSV is so configured OBO needs to set image links in e.g. Prometheus CRs that correspond to those configured image urls.

Our downstream release tooling needs to set the internally build image links in the CSV's spec.relatedImages field.

blocks

MON-3458 [CPAAS stage]COO should use released images

Closed

MON-3461 [CPASS-stage]Related images in csv doesn't include all the related images

Closed

is depended on by

OSPRH-800 Allow STF to be installed in a disconnected environment

Closed

is documented by

OBSDOCS-748 Release notes content for COO release 0.1.1

Closed

links to

OCP documentation around disconnected installations with OLM

RHEA-2023:124069 Cluster Observability Operator 0.1.1 for OpenShift

mentioned in: Page Loading...

(1 links to, 1 mentioned in)

Assignee:: Jan Fajerski

Reporter:: Jan Fajerski

Contributors:: Daniel Mellado Area

QA Contact:: Hongyan Li

Doc Contact:: Brian Burt

Votes:: 0 Vote for this issue

Watchers:: 8 Start watching this issue

Created:: 2023/11/02 3:48 PM

Updated:: 2024/01/29 3:44 PM

Resolved:: 2024/01/29 3:44 PM

Details

Description

Attachments

Issue Links

Activity

People

Dates