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>

cluster/examples/kubernetes/ceph/cluster-stretched-aws.yaml

@@ -22,7 +22,7 @@ spec:
     stretchCluster:
       # The ceph failure domain will be extracted from the label, which by default is the zone. The nodes running OSDs must have
       # this label in order for the OSDs to be configured in the correct topology. For topology labels, see
-      # https://rook.github.io/docs/rook/master/ceph-cluster-crd.html#osd-topology.
+      # https://rook.github.io/docs/rook/latest/ceph-cluster-crd.html#osd-topology.
       failureDomainLabel: topology.kubernetes.io/zone
       # The sub failure domain is the secondary level at which the data will be placed to maintain data durability and availability.
       # The default is "host", which means that each OSD must be on a different node and you would need at least two nodes per zone.

cluster/examples/kubernetes/ceph/cluster-stretched.yaml

@@ -22,7 +22,7 @@ spec:
     stretchCluster:
       # The ceph failure domain will be extracted from the label, which by default is the zone. The nodes running OSDs must have
       # this label in order for the OSDs to be configured in the correct topology. For topology labels, see
-      # https://rook.github.io/docs/rook/master/ceph-cluster-crd.html#osd-topology.
+      # https://rook.github.io/docs/rook/latest/ceph-cluster-crd.html#osd-topology.
       failureDomainLabel: topology.kubernetes.io/zone
       # The sub failure domain is the secondary level at which the data will be placed to maintain data durability and availability.
       # The default is "host", which means that each OSD must be on a different node and you would need at least two nodes per zone.

cluster/examples/kubernetes/ceph/cluster.yaml

@@ -33,7 +33,7 @@ spec:
   # Whether or not upgrade should continue even if a check fails
   # This means Ceph's status could be degraded and we don't recommend upgrading but you might decide otherwise
   # Use at your OWN risk
-  # To understand Rook's upgrade process of Ceph, read https://rook.io/docs/rook/master/ceph-upgrade.html#ceph-version-upgrades
+  # To understand Rook's upgrade process of Ceph, read https://rook.io/docs/rook/latest/ceph-upgrade.html#ceph-version-upgrades
   skipUpgradeChecks: false
   # Whether or not continue if PGs are not clean during an upgrade
   continueUpgradeAfterChecksEvenIfNotHealthy: false

cluster/examples/kubernetes/ceph/operator-openshift.yaml

@@ -138,7 +138,7 @@ data:
 
   # Enable Ceph Kernel clients on kernel < 4.17 which support quotas for Cephfs
   # If you disable the kernel client, your application may be disrupted during upgrade.
-  # See the upgrade guide: https://rook.io/docs/rook/master/ceph-upgrade.html
+  # See the upgrade guide: https://rook.io/docs/rook/latest/ceph-upgrade.html
   CSI_FORCE_CEPHFS_KERNEL_CLIENT: "true"
 
   # (Optional) policy for modifying a volume's ownership or permissions when the RBD PVC is being mounted.

cluster/examples/kubernetes/ceph/operator.yaml

@@ -58,7 +58,7 @@ data:
 
   # Enable cephfs kernel driver instead of ceph-fuse.
   # If you disable the kernel client, your application may be disrupted during upgrade.
-  # See the upgrade guide: https://rook.io/docs/rook/master/ceph-upgrade.html
+  # See the upgrade guide: https://rook.io/docs/rook/latest/ceph-upgrade.html
   # NOTE! cephfs quota is not supported in kernel version < 4.17
   CSI_FORCE_CEPHFS_KERNEL_CLIENT: "true"