Follow

Table of Contents 

User Documentation


Release 2.1.2

Release Date

  • May 11, 2022

InfiniBox CSI Driver 2.1.2 Improvements

  • The default Operator controller-manager memory has been increased
    • In environments that included many nodes, the memory limit for the Operator controller-manager pod was very low. The memory limit has been increased to accommodate a very large number of nodes.

InfiniBox CSI Driver 2.1.2 Changes

  • InfiniBox CSI Driver now includes the parameter 'hard' in the default NFS mount options
    • In accordance with Infinidat's best practice recommendations for setting up NAS services, the default NFS mount options now include 'hard'. This ensures that mounts are used with interrupts disabled so that there will be no file access disruptions. To override this feature, include 'soft' in the StorageClass mountOptions list.

InfiniBox CSI Driver 2.1.2 Fixed Issues

Severity Key Release Notes Title Release Notes Description
CriticalCSIC-383Early cleanup of mountpointsIn some cases, the driver tried to clean up mountpoints without unmounting relevant devices.
MinorCSIC-391To prevent mount errors, the NFS mount options now always include nfsvers=3InfiniBox CSI Driver 2.1.0 added 'nfsvers=3' to the default NFS mount options that are used whenever CSI 'mountOptions' or 'nfs_mount_options' (deprecated) parameters are not specified. However, if those parameters were specified and did not include 'nfsvers=3', then mounts could fail if hosts could not correctly negotiate to the NFSv3 protocol supported by InfiniBox. CSI Driver 2.1.2 now always appends 'nfsvers=3' to the options passed to the NFS mount command.

InfiniBox CSI Driver 2.1.2 Known Issues

Severity Key Release Notes Title Release Notes Description
MinorCSIC-364NFS export rules must always be specified in StorageClassDynamically provisioned nodes might not receive appropriate export rules after this release is installed.

Release 2.1.0

As of May 11, 2022, Infinibox CSI Driver 2.1.0 has been deprecated.

Release 2.1.2 incorporates all features from release 2.1.0 as well as improvements, changes, and fixes for issues discovered shortly after 2.1.0 was released.

Release Date

  • April 14, 2022

What's New in Release 2.1.0

  • Kubernetes 1.20-1.23 and derivatives are now supported
  • You can specify UNIX permissions for NFS- and iSCSI-based datasets
    • Use the new 'unix_permissions' parameter to 'chmod' your dataset mountpoint accordingly. Note: Currently, this is only supported for iSCSI and NFS, and not for TreeQs or Fibre Channel.
  • You can specify UID:GID ownership for NFS- and iSCSI-based dataset mount points
    • Use the new 'uid' and 'gid' parameters to automatically 'chown' your dataset mountpoint accordingly. Note: Currently, this is only supported for iSCSI and NFS, and not for TreeQs or Fibre Channel.
  • You can use NFS-based PVs over non-privileged TCP ports
    • Use the new 'privileged_ports_only' parameter to run NFS over unprivileged ports.
  • You can control visibility of the .snapshot directory for PVs using NFS
    • The 'snapdir_visible' parameter accommodates sensitive user workflows by controlling the presence of the .snapshot directory in NFS-based persistent volumes.

InfiniBox CSI Driver 2.1.0 Improvements

  • OpenShift Operator for InfiniBox CSI Driver has been completely redesigned
    • The InfiniBox CSI Driver has been rewritten to use the Operator SDK for greater standardization and functionality in current OpenShift environments, including re-publication to Red Hat OpenShift integrated OperatorHub.
  • The NFS mount version parameter is now explicitly set to NFSv3 which aligns with InfiniBox capabilities
  • The log formatting has been improved for clarity
  • Installation in OpenShift environments has been simplified by the automatic configuration of 'SecurityContextConstraints'
  • Asterisk wildcards are now supported for NFS exports

InfiniBox CSI Driver 2.1.0 Changes

  • A new mount option 'nouuid' handles duplicate UUIDs
    • In version 2.0.0, XFS UUIDs had to be regenerated whenever two filesystems with the same UUID were mounted. The mount option 'nouuid' now handles duplicate UUIDs so that configuration options are no longer required.
  • InfiniBox CSI Driver removes 'TargetPath' when 'NodeUnpublishVolume' is called
    • Previously, the kubelet removed 'TargetPath' when 'NodeUnpublishVolume' was called. For compatibility with Kubernetes 1.22 and above, the InfiniBox CSI Driver now removes it. 
  • InfiniBox CSI Driver now uses CSIDriver API v1, aligning to upstream community changes as well as to API extensions
    • Previously, the InfiniBox CSI Driver's API specified v1beta1. For compatibility with Kubernetes 1.22 and above, the API now specifies v1. 
  • For better alignment with OpenShift, Red Hat Universal Base Image (UBI) is now used in place of Ubuntu (18.04)
  • The standard 'FsType VolumeCapability' parameter replaces the proprietary 'fstype' parameter
    • Previously, when requesting a StorageClass that involved a host-generated filesystem backed by InfiniBox block storage, users needed to specify the filesystem type using the proprietary 'fstype' parameter. The InfiniBox CSI Driver now uses the standard CSI 'csi.storage.k8s.io/fstype' parameter instead.
  • The standard 'mountOptions' parameter replaces the proprietary 'nfs_mount_options' parameter
    • Previously, when requesting a StorageClass, users needed to provide mount options for NFS in a proprietary 'nfs_mount_options' string parameter. To provide more flexibility for users, and to align with the way these options are handled in other protocols, the InfiniBox CSI Driver now uses the standard CSI 'mountOptions' list parameter instead.

InfiniBox CSI Driver 2.1.0 Fixed Issues

SeverityKeyRelease Notes TitleRelease Notes Description
MajorCSIC-337Some AccessModes were rejectedPreviously, the InfiniBox CSI Driver incorrectly rejected all Fibre Channel and iSCSI datasets' AccessModes other than SINGLE_NODE_WRITER. Now, all AccessModes are accepted, and a warning message is shown for potentially dangerous multi-writer scenarios.
MajorCSIC-354Some host-side devices were not removed during volume deletionWhen the CSI DeleteVolume command was run for iSCSI datasets, leftover host devices were not always completely removed.  
MinorCSIC-332The InfiniBox CSI Driver treated all StorageClass parameters as required, and it sometimes generated unwarranted errors if optional parameters were not provided

InfiniBox CSI Driver 2.1.0 Known Issues

SeverityKeyRelease Notes TitleRelease Notes Description
MinorCSIC-364NFS export rules must always be specified in StorageClassDynamically provisioned nodes might not receive appropriate export rules after this release is installed.

Release 2.0.0

  • Release Date: May 21, 2021

What's new in this release

  • Implemented CSI snapshotter API v1 GA enabling snapshot support in Kubernetes 1.17+

The upstream Kubernetes CSI snapshot v1 beta/GA API is not backwards compatible with the earlier alpha CSI snapshot API (details here), so snapshots created previously using the CSI alpha API implemented in earlier Infinidat CSI driver versions need to be manually migrated. Contact Infinidat support if you have snapshots previously created that need to be preserved through this upgrade.

  • Improved clarity of the CSI driver logs for customer analysis and faster support
  • Improved multipathing configuration management
  • Improved iSCSI configuration and management
  • The CSI driver no longer supports Kubernetes releases earlier than 1.17
  • Improved OpenShift Operator for OpenShift 4.7+ 

Fixed issues

  • PSDEV-753 CSI driver fails to mount volumes in k8s 1.20
  • CSIC-192 When mounting copies of XFS filesystems the UUID is duplicated
  • CSIC-188 Catch if there is a discrepancy between k8s storage class request for read-write permissions and default read-only permission for snapshots
  • ZEN-28431 Cannot mount the image registry pod on OpenShift 4.7+ and on Kubernetes 1.20

Was this article helpful?
0 out of 0 found this helpful

0 out of 0 found this helpful

Last edited: 2022-08-06 08:43:24 UTC

Comments