Bug 2274358 - Failure Domain Topology Labels
Summary: Failure Domain Topology Labels
Keywords:
Status: NEW
Alias: None
Product: Red Hat OpenShift Data Foundation
Classification: Red Hat Storage
Component: documentation
Version: 4.14
Hardware: x86_64
OS: Unspecified
unspecified
medium
Target Milestone: ---
: ---
Assignee: Anjana Suparna Sriram
QA Contact: Neha Berry
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2024-04-10 14:47 UTC by Rick Martins
Modified: 2024-04-10 14:47 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description Rick Martins 2024-04-10 14:47:42 UTC
Describe the issue:

Existing documentation [1] that covers pod placement makes reference to external kubernetes documentation on the use of topology labels [2] but these don't cover all scenarios that customers are likely to want/need to use e.g rack. Specifically Rook has additional labels [3] which can be used to influence/define the topology. 


Describe the task you were trying to accomplish:

Deploy ODF across user defined failure domains as per design.


Suggestions for improvement:

We should either add this into our docs or at least add a link out to the Rook page explaining this for customers that need this info.


Document URL:

 [1] https://access.redhat.com/documentation/en-us/red_hat_openshift_data_foundation/4.14/html/planning_your_deployment/infrastructure-requirements_rhodf#pod-placement-rules_rhodf

 [2] https://kubernetes.io/docs/reference/labels-annotations-taints/#topologykubernetesiozone

 [3] https://rook.io/docs/rook/v1.12/CRDs/Cluster/ceph-cluster-crd/#osd-topology

Chapter/Section Number and Title:

Product Version:

ODF 4.14

Environment Details:

OCP 4.14 (both VMware and IBM Z)

Any other versions of this document that also needs this update:

Likely needs to be updated for a few platforms i.e. bare metal, IBM Z, VMware UPI etc. as well as multiple ODF versions.

Additional information:


Note You need to log in before you can comment on or make changes to this bug.