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>
2021-09-22 12:41:32 -06:00
1 parent 0ec1303606
commit 0591753673
@@ -1,7 +1,7 @@
 The Ceph Cluster has been installed. Check its status by running:
  kubectl --namespace {{ .Release.Namespace }} get cephcluster

-Visit https://rook.github.io/docs/rook/master/ceph-cluster-crd.html for more information about the Ceph CRD.
+Visit https://rook.github.io/docs/rook/latest/ceph-cluster-crd.html for more information about the Ceph CRD.

 Important Notes:
 - You can only deploy a single cluster per namespace
@@ -56,7 +56,7 @@ cephClusterSpec:
  # 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
@@ -1,7 +1,7 @@
 The Rook Operator has been installed. Check its status by running:
  kubectl --namespace {{ .Release.Namespace }} get pods -l "app=rook-ceph-operator"

-Visit https://rook.io/docs/rook/master for instructions on how to create and configure Rook clusters
+Visit https://rook.io/docs/rook/latest for instructions on how to create and configure Rook clusters

 Important Notes:
 - You must customize the 'CephCluster' resource in the sample manifests for your cluster.
@@ -13,7 +13,7 @@ crds:
  # managed independently with cluster/examples/kubernetes/ceph/crds.yaml.
  # **WARNING** Only set during first deployment. If later disabled the cluster may be DESTROYED.
  # If the CRDs are deleted in this case, see the disaster recovery guide to restore them.
-  # https://rook.github.io/docs/rook/master/ceph-disaster-recovery.html#restoring-crds-after-deletion
+  # https://rook.github.io/docs/rook/latest/ceph-disaster-recovery.html#restoring-crds-after-deletion
  enabled: true

 resources:
@@ -321,7 +321,7 @@ allowMultipleFilesystems: false
 #     effect: NoSchedule
 #   nodeAffinity: key1=value1,value2; key2=value3
 #   mountSecurityMode: Any
-## For information on FlexVolume path, please refer to https://rook.io/docs/rook/master/flexvolume.html
+## For information on FlexVolume path, please refer to https://rook.io/docs/rook/latest/flexvolume.html
 #   flexVolumeDirPath: /usr/libexec/kubernetes/kubelet-plugins/volume/exec/
 #   libModulesDirPath: /lib/modules
 #   mounts: mount1=/host/path:/container/path,/host/path2:/container/path2
@@ -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.
@@ -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.
@@ -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
@@ -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.
@@ -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"