OCPNAS#241: Refactor to address issues from UI statelesssness

Author: danielclowers

modules/virt-fusion-access-san-release-updates.adoc

@@ -4,22 +4,30 @@
 
 :_mod-docs-content-type: CONCEPT
 [id="virt-fusion-access-san-release-updates_{context}"]
-= IBM Fusion Access for SAN release updates
+= {IBMFusionFirst} release updates
 
 [role="_abstract"]
-Release updates for IBM Fusion Access for SAN, including new features, bug fixes, and known issues.
+Release updates for {IBMFusionFirst}, including new features, bug fixes, and known issues.
 
 [id="virt-fusion-access-san-new-changes_{context}"]
 == New and changed features
 
-Fusion Access for SAN 1.1.0 includes Spectrum Scale 5.2.3.5::
+{IBMFusionFirst} 1.1.0 includes Spectrum Scale 5.2.3.5::
 
-Fusion Access for SAN 1.1.0 uses Spectrum Scale version 5.2.3.5. When you upgrade to Fusion Access for SAN 1.1.0, Spectrum Scale is automatically upgraded to version 5.2.3.5.
+{IBMFusionFirst} 1.1.0 uses Spectrum Scale version 5.2.3.5. When you upgrade to {IBMFusionFirst} 1.1.0, Spectrum Scale is automatically upgraded to version 5.2.3.5.
 +
 link:https://issues.redhat.com/browse/OCPNAS-294[OCPNAS-294]
 +
 link:https://issues.redhat.com/browse/OCPNAS-279[OCPNAS-279]
 
+Backend redesign for `FileSystemClaim` resources::
+
+{IBMFusionFirst} updates the backend to use `FileSystemClaim` resources for managing filesystem related objects. Previously, filesystem creation could fail if the process was interrupted. With this update, backend handling improves reliability while keeping the user interface flow and appearance unchanged.
++
+After upgrading to {IBMFusionFirst} 1.1.0, resources that were created by using the 1.0 user interface are automatically migrated and associated with a `FileSystemClaim` resource.
++
+link:https://issues.redhat.com/browse/OCPNAS-241[OCPNAS-241]
+
 Image registry requirements for kernel module management::
 
 {IBMFusionFirst} uses the {product-title} image registry to manage the kernel module. Do not configure the registry to use `emptyDir` storage because it provides only temporary storage and is not suitable for production use. Configure {IBMFusionFirst} to use a different image registry by creating a config map and secret after installing the Operator and before creating the `FusionAccess` CR.