Merge branch 'main' into gh-issue-31

earlier-versions.adoc

@@ -11,12 +11,11 @@ summary: Documentation for previous releases of Astra Trident is available in ca
 :imagesdir: ../media/
 
 [.lead]
-The documentation for previous releases of Astra Trident is available in case you’re not running the latest version.
+If you aren't running Astra Trident 21.10, the documentation for previous releases is available.
 
-NOTE: The documentation for Astra Trident 21.07 and associated patch releases is https://docs.netapp.com/us-en/trident-2107/index.html[here^].
-
-NOTE: The documentation for earlier versions of Astra Trident is in our legacy documentation site.
+NOTE: For releases prior to 21.07, you will be redirected to the legacy documentation site.
 
+* https://docs.netapp.com/us-en/trident-2107/index.html[Astra Trident 21.07^]
 * https://netapp-trident.readthedocs.io/en/stable-v21.04/[Astra Trident 21.04^]
 * https://netapp-trident.readthedocs.io/en/stable-v21.01/[Astra Trident 21.01^]
 * https://netapp-trident.readthedocs.io/en/stable-v20.10/[Astra Trident 20.10^]

trident-get-started/requirements.adoc

@@ -125,56 +125,69 @@ For air-gapped installations, see the following list for what container images a
 
 |v1.17.0
 a|
-* netapp/trident:21.07.0
-* netapp/trident-operator:21.07.0
-* netapp/trident-autosupport:21.01
-* k8s.gcr.io/sig-storage/csi-provisioner:v2.1.1
-* k8s.gcr.io/sig-storage/csi-attacher:v3.1.0
-* k8s.gcr.io/sig-storage/csi-resizer:v1.1.0
+* netapp/trident:21.10.0
+* netapp/trident-autosupport:21.10
+* k8s.gcr.io/sig-storage/csi-provisioner:v2.2.2
+* k8s.gcr.io/sig-storage/csi-attacher:v3.3.0
+* k8s.gcr.io/sig-storage/csi-resizer:v1.3.0
 * k8s.gcr.io/sig-storage/csi-snapshotter:v3.0.3
-* k8s.gcr.io/sig-storage/csi-node-driver-registrar:v2.1.0
+* k8s.gcr.io/sig-storage/csi-node-driver-registrar:v2.3.0
+* netapp/trident-operator:21.10.0 (optional)
 
 |v1.18.0
 a|
-* netapp/trident:21.07.0
-* netapp/trident-operator:21.07.0
-* netapp/trident-autosupport:21.01
-* k8s.gcr.io/sig-storage/csi-provisioner:v2.1.1
-* k8s.gcr.io/sig-storage/csi-attacher:v3.1.0
-* k8s.gcr.io/sig-storage/csi-resizer:v1.1.0
+* netapp/trident:21.10.0
+* netapp/trident-autosupport:21.10
+* k8s.gcr.io/sig-storage/csi-provisioner:v2.2.2
+* k8s.gcr.io/sig-storage/csi-attacher:v3.3.0
+* k8s.gcr.io/sig-storage/csi-resizer:v1.3.0
+* k8s.gcr.io/sig-storage/csi-snapshotter:v3.0.3
+* k8s.gcr.io/sig-storage/csi-node-driver-registrar:v2.3.0
+* netapp/trident-operator:21.10.0 (optional)
 
 |v1.19.0
 a|
-* netapp/trident:21.07.0
-* netapp/trident-operator:21.07.0
-* netapp/trident-autosupport:21.01
-* k8s.gcr.io/sig-storage/csi-provisioner:v2.1.1
-* k8s.gcr.io/sig-storage/csi-attacher:v3.1.0
-* k8s.gcr.io/sig-storage/csi-resizer:v1.1.0
+* netapp/trident:21.10.0
+* netapp/trident-autosupport:21.10
+* k8s.gcr.io/sig-storage/csi-provisioner:v2.2.2
+* k8s.gcr.io/sig-storage/csi-attacher:v3.3.0
+* k8s.gcr.io/sig-storage/csi-resizer:v1.3.0
 * k8s.gcr.io/sig-storage/csi-snapshotter:v3.0.3
-* k8s.gcr.io/sig-storage/csi-node-driver-registrar:v2.1.0
+* k8s.gcr.io/sig-storage/csi-node-driver-registrar:v2.3.0
+* netapp/trident-operator:21.10.0 (optional)
 
 |v1.20.0
 a|
-* netapp/trident:21.07.0
-* netapp/trident-operator:21.07.0
-* netapp/trident-autosupport:21.01
-* k8s.gcr.io/sig-storage/csi-provisioner:v2.1.1
-* k8s.gcr.io/sig-storage/csi-attacher:v3.1.0
-* k8s.gcr.io/sig-storage/csi-resizer:v1.1.0
-* k8s.gcr.io/sig-storage/csi-snapshotter:v4.1.1
-* k8s.gcr.io/sig-storage/csi-node-driver-registrar:v2.1.0
+* netapp/trident:21.10.0
+* netapp/trident-autosupport:21.10
+* k8s.gcr.io/sig-storage/csi-provisioner:v3.0.0
+* k8s.gcr.io/sig-storage/csi-attacher:v3.3.0
+* k8s.gcr.io/sig-storage/csi-resizer:v1.3.0
+* k8s.gcr.io/sig-storage/csi-snapshotter:v3.0.3
+* k8s.gcr.io/sig-storage/csi-node-driver-registrar:v2.3.0
+* netapp/trident-operator:21.10.0 (optional)
 
 |v1.21.0
 a|
-* netapp/trident:21.07.0
-* netapp/trident-operator:21.07.0
-* netapp/trident-autosupport:21.01
-* k8s.gcr.io/sig-storage/csi-provisioner:v2.1.1
-* k8s.gcr.io/sig-storage/csi-attacher:v3.1.0
-* k8s.gcr.io/sig-storage/csi-resizer:v1.1.0
-* k8s.gcr.io/sig-storage/csi-snapshotter:v4.1.1
-* k8s.gcr.io/sig-storage/csi-node-driver-registrar:v2.1.0
+* netapp/trident:21.10.0
+* netapp/trident-autosupport:21.10
+* k8s.gcr.io/sig-storage/csi-provisioner:v3.0.0
+* k8s.gcr.io/sig-storage/csi-attacher:v3.3.0
+* k8s.gcr.io/sig-storage/csi-resizer:v1.3.0
+* k8s.gcr.io/sig-storage/csi-snapshotter:v3.0.3
+* k8s.gcr.io/sig-storage/csi-node-driver-registrar:v2.3.0
+* netapp/trident-operator:21.10.0 (optional)
+
+|v1.22.0
+a|
+* netapp/trident:21.10.0                                  
+* netapp/trident-autosupport:21.10
+* k8s.gcr.io/sig-storage/csi-provisioner:v3.0.0
+* k8s.gcr.io/sig-storage/csi-attacher:v3.3.0
+* k8s.gcr.io/sig-storage/csi-resizer:v1.3.0
+* k8s.gcr.io/sig-storage/csi-snapshotter:v3.0.3
+* k8s.gcr.io/sig-storage/csi-node-driver-registrar:v2.3.0
+* netapp/trident-operator:21.10.0 (optional)
 
 |===
 

trident-reference/tridentctl.adoc

@@ -15,7 +15,7 @@ The https://github.com/NetApp/trident/releases[Trident installer bundle^] includ
 
 For usage information, run `tridentctl --help`.
 
-The available commands and global options are as follows:
+The available commands and global options are:
 ----
 Usage:
   tridentctl [command]
@@ -125,6 +125,7 @@ Flags:
 * ``--enable-node-prep`: Attempt to install required packages on nodes.
 * ``--generate-custom-yaml`: Generate YAML files without installing anything.
 * ``-h, --help`: Help for install.
+//* ``--http-request-timeout`: Override the HTTP request timeout for Trident controller’s REST API (default 1m30s).
 * ``--image-registry string`: The address/port of an internal image registry.
 * ``--k8s-timeout duration`: The timeout for all Kubernetes operations (default 3m0s).
 * ``--kubelet-dir string`: The host location of kubelet's internal state (default "/var/lib/kubelet").

trident-rn.adoc

@@ -16,7 +16,7 @@ WARNING: The `tridentctl` binary for Linux that is provided in the installer zip
 
 == What's new in 21.10
 
-NetApp is continually improving and enhancing its products and services. Here are some of the latest features and functionalities available with Astra Trident.
+NetApp is continually improving and enhancing its products and services. Here are some of the latest features in Astra Trident.
 
 For previous releases, see https://docs.netapp.com/us-en/trident/earlier-versions.html[Ealier versions of documentation].
 

trident-use/gcp.adoc

@@ -68,11 +68,11 @@ See the following table for the backend configuration options:
 
 If using a shared VPC network, both `projectNumber` and `hostProjectNumber` must be specified. In that case, `projectNumber` is the service project, and `hostProjectNumber` is the host project.
 
-The `apiRegion` represents the GCP region where Astra Trident creates CVS volumes. Astra Trident can mount and attach volumes on Kubernetes nodes that belong to the same GCP region. When creating a backend, it is important to ensure `apiRegion` matches the region Kubernetes nodes are deployed in. When creating cross-region Kubernetes clusters, CVS volumes that are created in a given `apiRegion` can only be used in workloads scheduled on nodes that are in the same GCP region.
+The `apiRegion` represents the GCP region where Astra Trident creates CVS volumes. Astra Trident can mount and attach volumes on Kubernetes nodes that belong to the same GCP region. When creating a backend, it is important to ensure `apiRegion` matches the region Kubernetes nodes are deployed in. When creating cross-region Kubernetes clusters, CVS cloud volumes that are created in a given `apiRegion` can only be used in workloads scheduled on nodes that are in the same GCP region.
 
 NOTE: `storageClass` is an optional parameter that you can use to select the desired https://cloud.google.com/solutions/partners/netapp-cloud-volumes/service-types?hl=en_US[CVS service type^]. You can choose from the base CVS service type (`storageClass=software`) or the CVS-Performance service type (`storageClass=hardware`), which Trident uses by default. Make sure you specify an `apiRegion` that provides the respective CVS `storageClass` in your backend definition.
 
-IMPORTANT: Astra Trident's integration with the base CVS service type on Google Cloud is a **beta feature**, not meant for production workloads. Trident is **fully supported** with the CVS-Performance service type and uses it by default.
+CAUTION: Astra Trident's integration with the base CVS service type on Google Cloud is a **beta feature**, not meant for production workloads. Trident is **fully supported** with the CVS-Performance service type and uses it by default.
 
 Each backend provisions volumes in a single Google Cloud region. To create volumes in other regions, you can define additional backends.
 

trident-use/vol-snapshots.adoc

@@ -32,6 +32,8 @@ kubectl apply -f https://raw.githubusercontent.com/kubernetes-csi/external-snaps
 ----
 . Create the snapshot-controller in the desired namespace. Edit the YAML manifests below to modify namespace.
 +
+NOTE: Don’t create a snapshot-controller if setting up on-demand volume snapshots in a GKE environment. GKE uses a built-in, hidden snapshot-controller.
+
 ----
 kubectl apply -f https://raw.githubusercontent.com/kubernetes-csi/external-snapshotter/release-3.0/deploy/kubernetes/snapshot-controller/rbac-snapshot-controller.yaml
 kubectl apply -f https://raw.githubusercontent.com/kubernetes-csi/external-snapshotter/release-3.0/deploy/kubernetes/snapshot-controller/setup-snapshot-controller.yaml

trident-use/worker-node-prep.adoc

@@ -67,7 +67,10 @@ a|
 `sudo sed -i 's/^\(node.session.scan\).*/\1 = manual/' /etc/iscsi/iscsid.conf`
 . Enable multipathing:
 +
-`sudo mpathconf --enable --with_multipathd y`
+`sudo mpathconf --enable --with_multipathd y --find_multipaths n`
++
+NOTE: Ensure `etc/multipath.conf` contains `find_multipaths no` under `defaults`.
+
 . Ensure that `iscsid` and `multipathd` are running:
 +
 `sudo systemctl enable --now iscsid multipathd`
@@ -92,11 +95,14 @@ a|
 `sudo tee /etc/multipath.conf <<-'EOF'
 defaults {
     user_friendly_names yes
-    find_multipaths yes
+    find_multipaths no
 }
 EOF
 sudo systemctl enable --now multipath-tools.service
 sudo service multipath-tools restart`
++
+NOTE: Ensure `etc/multipath.conf` contains `find_multipaths no` under `defaults`.
+
 . Ensure that `open-iscsi` and `multipath-tools` are enabled and running:
 +
 `sudo systemctl status multipath-tools`