Updates for context

trident-get-started/requirements.adoc

@@ -63,7 +63,6 @@ To use Trident, you need one or more of the following supported backends:
 Trident supports the following ONTAP drivers for KubeVirt and OpenShift Virtualization:
 
 * ontap-nas
-* ontap-nas-economy
 * ontap-san (iSCSI, FCP, NVMe over TCP)
 * ontap-san-economy (iSCSI Only)
 
@@ -166,7 +165,7 @@ For air-gapped installations, the following list is a reference of container ima
 |Kubernetes versions
 |Container image
 
-| v1.27.0, v1.28.0, v1.29.0, v1.30.0, v1.31.0, v1.32.0, v1.33.0, v1.35.0
+| v1.27.0, v1.28.0, v1.29.0, v1.30.0, v1.31.0, v1.32.0, v1.33.0, v1.34.0, v1.35.0
 a|
 * docker.io/netapp/trident:26.02.0                      
 * docker.io/netapp/trident-autosupport:26.02                   

trident-rn.adoc

@@ -108,7 +108,7 @@ Learn what's new in Trident and Trident Protect, including enhancements, fixes,
 ** Added an option `--no-rename` when importing a volume to retain the original name but let Trident manage the volume's lifecycle. See link:https://docs.netapp.com/us-en/trident/trident-use/vol-import.html[Import volumes^].
 ** Trident deployment now runs at the system-cluster-critical priority class. 
 * Added an option for Trident controller to use host networking via helm, operator, and tridentctl (link:https://github.com/NetApp/trident/issues/858[Issue #858]).
-* Added manual QoS support to the ANF driver, making it production-ready in Trident 26.02; this experimental enhancement was introduced in Trident 25.06.
+* Added manual QoS support to the ANF driver, making it production-ready in Trident 25.10; this experimental enhancement was introduced in Trident 25.06.
 
 ==== Experimental Enhancements
 NOTE: Not for use in production environments.

trident-use/automatic-volume-expansion.adoc

@@ -28,10 +28,10 @@ Before configuring automatic volume expansion, ensure that the following require
 * Role-based access control permissions to create `TridentAutogrowPolicy` custom resources
 * StorageClasses configured with `allowVolumeExpansion: true`
 * Supported ONTAP protocols:
-** Network File System
-** Internet Small Computer Systems Interface
-** Fibre Channel Protocol
-** Non-Volatile Memory Express over Fabrics
+** Network File System (NFS)
+** Internet Small Computer Systems Interface (iSCSI)
+** Fibre Channel Protocol (NVMe)
+** Non-Volatile Memory Express over Fabrics (FCP)
 
 == Limitations
 
@@ -40,10 +40,10 @@ Before configuring automatic volume expansion, ensure that the following require
 * In brownfield environments, automatic expansion might not function for certain existing volumes due to volume publication migration behavior.
 * When a volume reaches `maxSize`, no further expansion occurs.
 * Supported protocols for automatic volume expansion:
-** Network File System
-** Internet Small Computer Systems Interface
-** Fibre Channel Protocol
-** Non-Volatile Memory Express over Fabrics
+** Network File System (NFS)
+** Internet Small Computer Systems Interface (iSCSI)
+** Fibre Channel Protocol (NVMe)
+** Non-Volatile Memory Express over Fabrics (FCP)
 
 == Provision Volumes with Autogrow Policy
 

trident-use/controller-scalability.adoc

@@ -11,10 +11,7 @@ summary: Understand controller scalability, concurrency behavior, and feature ma
 :imagesdir: ../media/
 
 [.lead]
-Trident introduces controller scalability through improved concurrency across multiple storage drivers.
-Customers can identify which Trident drivers support controller scalability at general availability and which drivers are available as a technical preview in Trident 26.02.
-This enables informed deployment decisions and appropriate risk management for scalable Kubernetes environments.
-
+Trident introduces controller scalability through improved concurrency across multiple storage drivers. Customers can identify which Trident drivers support controller scalability at general availability and which drivers are available as a technical preview in Trident 26.02. This enables informed deployment decisions and appropriate risk management for scalable Kubernetes environments.
 
 == Key concepts and definitions
 
@@ -23,8 +20,7 @@ This enables informed deployment decisions and appropriate risk management for s
 Controller scalability refers to the Trident controller's ability to process multiple storage operations in parallel rather than serializing them behind a single lock.
 These operations include volume creation, deletion, resizing, snapshot creation and deletion, volume publish and unpublish, and backend management.
 
-When controller scalability is enabled, operations on different volumes and backends proceed concurrently.
-This increases throughput and reduces end-to-end operation time in environments with high numbers of concurrent PersistentVolumeClaim and VolumeSnapshot operations.
+When controller scalability is enabled, operations on different volumes and backends proceed concurrently. This increases throughput and reduces end-to-end operation time in environments with high numbers of concurrent PersistentVolumeClaim and VolumeSnapshot operations.
 
 == Controller scalability support
 
@@ -34,11 +30,16 @@ Trident supports controller scalability with different maturity levels depending
 
 The following drivers support controller scalability at general availability in Trident 26.02:
 
-* `san`
-* `nas`
-* `san-nvme`
+* `ontap-san`
+* `ontap-nas`
 * `google-cloud-netapp-volumes`
 
+[NOTE]
+====
+The `google-cloud-netapp-volumes` and `google-cloud-netapp-volumes-san` drivers are different. 
+Only `google-cloud-netapp-volumes` is supported. Do not use `google-cloud-netapp-volumes-san` in backend configurations or examples.
+====
+
 
 == Enable controller scalability
 

trident-use/gcnv.adoc

@@ -39,7 +39,7 @@ require block-level access or application-managed I/O behavior.
 This applies to the following environments:
 
 * Trident 26.02 and later
-* Google Kubernetes Engine (GKE)
+* Google Kubernetes Engine (GKE) or Red Hat OpenShift
 * Google Cloud NetApp Volumes NAS pools
 * NFS and SMB workloads
 

trident-use/vol-import.adoc

@@ -286,6 +286,58 @@ image:./san-import-igroup.png[Image of LUNS mapped to iqn and cluster iqn.]
 --
 ====
 
+== ONTAP SAN-economy examples
+
+The following examples show how to import managed and unmanaged volumes for the `ontap-san-economy` backend.
+
+[role="tabbed-block"]
+====
+
+.Managed volume
+--
+When you import a managed volume, Trident takes ownership of the FlexVol and renames it. You must account for this renaming when you import multiple LUNs from the same FlexVol.
+
+The following example imports `lun1` from the FlexVol `toimport` as a managed volume named `vol-managed-saneco`:
+
+----
+tridentctl import volume vol-managed-saneco toimport/lun1 -f import1.yaml
+----
+
+After importing `lun1`, Trident renames the FlexVol (for example, to `trident_lun_pool_xyz`). To import additional LUNs from the same FlexVol, use the new FlexVol name:
+
+----
+tridentctl import volume vol-managed-saneco trident_lun_pool_xyz/lun2 -f import2.yaml
+----
+
+NOTE: The `ontap-san-economy` backend imports one LUN at a time. You can automate multiple imports using a script.
+--
+
+.Unmanaged volume
+--
+When you import an unmanaged volume, Trident does not take ownership of the FlexVol. However, the FlexVol and LUN must follow Trident naming conventions.
+
+FlexVol naming format::
++
+----
+trident_lun_pool_STORAGEPREFIX_RANDOMSTRING
+----
++
+* `STORAGEPREFIX` is the value of `storagePrefix` in your backend configuration. The default is `trident`.
+* `RANDOMSTRING` is any string you choose.
+
+LUN naming requirement::
+The LUN must be named `lun0`.
+
+Example::
+If your `storagePrefix` is `xyz`, the full path to the LUN is:
++
+----
+trident_lun_pool_xyz_randomstring/lun0
+----
+--
+
+====
+
 === Element
 Trident supports NetApp Element software and NetApp HCI volume import using the `solidfire-san` driver.