v4.0.18

• by default don't include frontend container on backends
• support custom ingress rules
• support cluster creation with no FS
• support using existing application insights from different subscription

v4.0.17

• smb_cluster_name variable is limited to 15 characters or less to align with the NetBIOS naming requirements.

v4.0.16

• Deployments now handled via WEKA clusterization only account, protecting Admin password during setup. Password for Admin user available from Key Vault upon cluster setup completing.
• No default hard coded WEKA version anymore. The latest deployment version must be specified with the ‘weka_version’ variable.
• Azure Storage Account access is now permitted in three different modes for greater flexibility: Disabled, EnabledForVnet, Enabled.
• Azure Storage Account access can now be configured with specified allowed IPs.
• DNS Zone usage is now optional.
• VMSS for WEKA clients is now supported.

v4.0.14

• Updated WEKA default version to 4.2.12.87

v4.0.13

• Updated WEKA default version to 4.2.11

v4.0.12

• Updated WEKA default version to 4.2.12
• Ability to provision WEKA S3 protocol servers
• Added support for Lasv3-series VMs as WEKA backends. These AMD 3rd Gen processor powered VMs enable customer choice in allowing selection between Intel powered Lsv3 VMs and now AMD powered Lasv3 VMs as WEKA backends.
• Added support for scale-out of NFS protocol servers.

v4.0.11

• Updated WEKA default version to 4.2.11.
• Added support for detecting client architecture of officially supported Arm clients.

v4.0.10

• Updated WEKA default version to 4.2.10. For deploying 4.3.0, please change the WEKA version in the Terraform main.tf file
• WEKA POSIX client is now supported on Azure VM instances powered by Ampere ARM based processors, and requires WEKA version 4.3.0 and above. See docs.weka.io for the full list of supported instances.
• By default, public IP assignment is now set to false when deploying WEKA on an existing network. It remains true when creating a new network for WEKA deployment.
• Added support for Standard_L80s_v3 VM instance as WEKA backend.
• Removed default resource tagging to enable management flexibility.
• Flexibility to use either existing or create new identities for WEKA deployment.

v4.0.9

• Updated WEKA default version to 4.2.9.28

v4.0.8

• Upgrading from version v4.0.7 to v4.0.8 requires removal of VMSS from the Terraform state. Use the command: terraform state rm module.weka_deployment.azurerm_linux_virtual_machine_scale_set.vmss .
• Updated WEKA default version to 4.2.9-1.
• Improved the retry logic for fetching the deployment script.
• Implemented automatic replacement of bad instances during clusterization.
• Extended WEKA cluster creation progress report info and added a summary.
• Added bad drives handling in clusterization: machines with bad drives will be deactivated.
• Removed SMB share from the installation script.
• Updated the clusterization target by adding a new variable clusterization_target. When this variable isn’t provided, the following formula is used: min(var.cluster_size, max(20, ceil(var.cluster_size * 0.8))).
  Added tags to clients.
• Moved VMSS instances creation to a function and supported config update.
• Added a warning in Terraform for unsupported regions.
• Added a custom_data variable for the clients module.