docs: update master doc links to latest
With the renaming of master docs to latest, all the links also need to be updated. Signed-off-by: Travis Nielsen <tnielsen@redhat.com>
This commit is contained in:
22 files changed
+30
-30
No files matched your search
+1
-1
@@ -1,3 +1,3 @@
|
||||
# Rook Feature Proposal
|
||||
|
||||
Please follow the [design section guideline](https://rook.io/docs/rook/master/development-flow.html#design-document).
|
||||
Please follow the [design section guideline](https://rook.io/docs/rook/latest/development-flow.html#design-document).
|
||||
@@ -54,7 +54,7 @@ The topology of the K8s cluster is to be determined by the admin, outside the sc
|
||||
Rook will simply detect the topology labels that have been added to the nodes.
|
||||
|
||||
If the desired failure domain is a "zone", the `topology.kubernetes.io/zone` label should
|
||||
be added to the nodes. Any of the [topology labels](https://rook.io/docs/rook/master/ceph-cluster-crd.html#osd-topology)
|
||||
be added to the nodes. Any of the [topology labels](https://rook.io/docs/rook/latest/ceph-cluster-crd.html#osd-topology)
|
||||
supported by OSDs can be used.
|
||||
|
||||
In the minimum configuration, two nodes in each data zone would be labeled, while one
|
||||
@@ -89,7 +89,7 @@ three zones must be listed and the arbiter zone is identified.
|
||||
stretchCluster:
|
||||
# The cluster is most commonly stretched over zones, but could also be stretched over
|
||||
# another failure domain such as datacenter or region. Must be one of the labels
|
||||
# used by OSDs as documented at https://rook.io/docs/rook/master/ceph-cluster-crd.html#osd-topology.
|
||||
# used by OSDs as documented at https://rook.io/docs/rook/latest/ceph-cluster-crd.html#osd-topology.
|
||||
failureDomainLabel: topology.kubernetes.io/zone
|
||||
zones:
|
||||
# There must be exactly three zones in this list, with one of them being the arbiter
|
||||
|
||||
Reference in new issue
Block a user