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.

v4.0.4

• remove smb share from installation script
• update default weka version: 4.2.8.66
• allow creating vpcs without subnets
• fix: iam: don't override existing members

v4.0.3

• add nat support
• add suport for host project for network and service project for deployment
• set default MTU to 8896
• fix udp support
• support Gvnic with UDP
• fix iam binding: don't override existing binding
• update weka default version: 4.2.7.64
• allow running TF from windows

v4.0.2

• align with weka default smbw config

v4.0.1

• update default weka version to 4.2.6.90

v4.0.0

• Stateless clients support
• Support user provided mtu
• NFS protocol GW support
• SMB protocol GW support
• Support provided weka proxy url
• Support provided weka home url
• Support creating weka api rule in the SG
• Setup ssh key on vms
• Fix: change secrets replication to regional
• Add missing partition and disk definition
• Emit weka events on scaling up/down
• Cross cloud variables alignment

v3.0.7

• fix: core ids calculation

v3.0.6

• update default weka version: 4.2.5

v3.0.5

• update default weka version to 4.2.4

Upgrade process:

• Upgrade from 3.0.4 to 3.0.5 requires only change of version on module invocation level, however, changes in this release on top of 3.0.4 apply only to new deployments
• Upgrade performed by changing module invocation, e.g by changing from

module "weka" {
  source  = "weka/weka/gcp"
  version = "3.0.4"
}

to

module "weka" {
  source  = "weka/weka/gcp"
  version = "3.0.5"
}

• If github/local/custom distribution is used and not hashicorp registry - update module invocation accordingly per used distribution method
• Upgrade from WEKA Terraform module versions 3.0.0 through 3.0.3 to 3.0.5 requires an additional step listed below before changing the Terraform module version: terraform state rm module.deploy_weka.null_resource.terminate-cluster
• Upgrade from WEKA Terraform module versions 2.0.x to 3.0.x is not supported. Migration can be done via WEKA Snap-To-Object feature into new WEKA cluster deployed by Terraform module version 3.0.5 or higher

v3.0.4

• fix: improve client/backend ip collision handling

Upgrade process:

• Upgrade from WEKA Terraform module versions 2.0.x to 3.0.4 (or higher) is not supported. Migration can be done via WEKA Snap-To-Object feature into new WEKA cluster deployed by Terraform module version 3.0.4 (or higher).
• Upgrade from WEKA Terraform module versions 3.0.0 through 3.0.3 to 3.0.4 (or higher) requires an additional step listed below before changing the Terraform module version.
  terraform state rm module.deploy_weka.null_resource.terminate-cluster