v4.0.14

• Fix: status function failure after upgrade from version 4.0.8 and below

v4.0.13

• Scaling up of NFS protocol servers can be performed using the ‘resize cluster command’ as provided by the Terraform outputs. Include "protocol":"nfs" in the request field. Example: '{"value":ENTER_NEW_VALUE_HERE,”protocol”:”nfs”}’.
• Upgrade of WEKA clusters with NFS protocol servers provisioned via Terraform prior to this release will require removing the state of NFS resources from the Terraform State file. This can be accomplished by running this command:
  $ terraform state rm "module.weka_deployment.module.nfs_protocol_gateways[0].google_compute_instance_from_template.this"
• Option to configure cross region access to the Load Balancer. E.g. This allows WEKA UI to be accessed from different regions.
• The GCP Provider requirement is now more flexible, allowing using newer provider versions.
• Deployments now handled via WEKA clusterization only account, protecting Admin password during setup. Password for Admin user available from Secret Manager upon cluster setup completing.
• No default hard coded WEKA version anymore. The latest deployment version must be specified with the ‘weka_version’ variable.

v4.0.12

• Updated WEKA default version to 4.2.12.87

v4.0.11

• Updated WEKA default version to 4.2.11

v4.0.10

• Updated WEKA default version to 4.2.12

v4.0.9 🌈

• Rocky 8.9 is now the default OS image deployed when provisioning WEKA backends.
  Other supported OSs are listed here: https://docs.weka.io/planning-and-installation/prerequisites-and-compatibility#operating-system
• Ability to provision WEKA S3 protocol servers

v4.0.8

• Updated WEKA default version to 4.2.11.
• Subnet firewall will not be created in case there are no subnets, or no subnet range provided in the network module of the WEKA Terraform package.
• Added support for UDP mode for WEKA backends.

v4.0.7

• Updated WEKA default version to 4.2.10. For deploying 4.3.0, please change the WEKA version in the Terraform main.tf file
• 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.

v4.0.6

• Updated WEKA default version to 4.2.9.28

v4.0.5

• Updated WEKA default version to 4.2.9-1.
• Introduced a new variable dns_zone_project_id to the root module. By default, it uses the network project ID.
• Added a new variable peering_name to our peering modules, allowing the overriding of the peering name.