Loading...

XML

Word

Printable

Type: Task
Resolution: Done
Priority: Blocker
Fix Version/s: Distributed Tracing 3.5
Affects Version/s: None
Component/s: Distributed Tracing
Labels:
- Distributed_Tracing

Story Points:
3
Blocked:
False
Blocked Reason:

Hide

None

Show
None
Ready:
False
Epic Link:
Distributed Tracing 3.5 Docs Epic
Git Pull Request:
https://github.com/openshift/openshift-docs/pull/88252, https://github.com/openshift/openshift-docs/pull/89145
Intelligence Requested:
Market:

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

TP or GA?

Add the docs about the support for IBM Cloud Object Storage in Tempo.

documents

TRACING-5080 Document support for IBM object store

Closed

is caused by

TRACING-4880 Add support to IBM Cloud Object Storage in Tempo

Release Pending

is related to

OBSDOCS-1605 [OBSDA-913] Add support to IBM Cloud Object Storage in Tempo

Release Pending

links to

openshift/openshift-docs#89145: OBSDOCS-1618: Document IBM Cloud Object Storage for Tempo

openshift/openshift-docs#90534: [enterprise-4.12] OBSDOCS-1618: Document IBM Cloud Object Storage for Tempo

openshift/openshift-docs#90535: [enterprise-4.13] OBSDOCS-1618: Document IBM Cloud Object Storage for Tempo

openshift/openshift-docs#90536: [enterprise-4.14] OBSDOCS-1618: Document IBM Cloud Object Storage for Tempo

openshift/openshift-docs#90537: [enterprise-4.15] OBSDOCS-1618: Document IBM Cloud Object Storage for Tempo

openshift/openshift-docs#90538: [enterprise-4.16] OBSDOCS-1618: Document IBM Cloud Object Storage for Tempo

openshift/openshift-docs#90539: [enterprise-4.17] OBSDOCS-1618: Document IBM Cloud Object Storage for Tempo

openshift/openshift-docs#90540: [enterprise-4.18] OBSDOCS-1618: Document IBM Cloud Object Storage for Tempo

openshift/openshift-docs#90541: [enterprise-4.19] OBSDOCS-1618: Document IBM Cloud Object Storage for Tempo

(7 links to)

Assignee:: Max Leonov

Reporter:: Max Leonov

Votes:: 0 Vote for this issue

Watchers:: 1 Start watching this issue

Created:: 2025/01/14 10:25 AM

Updated:: 2025/12/09 6:57 PM

Resolved:: 2025/03/19 6:42 PM