openshift/openshift-docs
1
0
Fork 0
mirror of https://github.com/openshift/openshift-docs.git synced 2026-02-05 12:46:18 +01:00
Code Issues Releases Activity

OCPNAS#293: RN - Missing SnapshotClass when creating filesystem

Browse Source
This commit is contained in:
danielclowers
2025-12-15 11:23:15 -05:00
committed by openshift-cherrypick-robot
parent 50f9be108b
commit 9a9162227a
1 changed files with 9 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
modules/virt-fusion-access-san-release-updates.adoc
View File

@@ -24,10 +24,18 @@ 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.
After you upgrade 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]
Automatic creation of `VolumeSnapshotClass` resources for filesystems::
{IBMFusionFirst} now creates a `VolumeSnapshotClass` resource alongside the `StorageClass` resource for each filesystem. This ensures that snapshot support is consistently available for newly created filesystems.
+
After upgrading from {IBMFusionFirst} 1.0 to 1.1.0, a `VolumeSnapshotClass` resource is automatically created for existing filesystems that did not previously have one.
+
link:https://issues.redhat.com/browse/OCPNAS-293[OCPNAS-293]
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.