v1.0.18

• support custom prefixes
• support configurable root volume size
• by default don't include frontend container on backends
• support custom ingress rules
• support cluster creation with no FS

v1.0.17

• EBS encryption is now on by default for better security of the data.
• smb_cluster_name variable is limited to 15 characters or less to align with the NetBIOS naming requirements.

v1.0.16

• Added support for s3 url for install_weka_url
• Added support for custom lambdas zip location (by providing lambdas_custom_s3_bucket ,lambdas_custom_s3_key)

v1.0.15

• No default hard coded WEKA version anymore. The latest deployment version must be specified with the ‘weka_version’ variable
• Deployments now handled via WEKA clusterization only account, protecting Admin password during setup. Password for Admin user available from AWS Secrets Manager upon cluster setup completing.
• Support for capacity reservation parameter when creating the launch template for WEKA cluster backends
• Placement group usage for the EC2 instances running WEKA is now optional (enabled by default)
• All created resources will now have the proper tags_map propagated
• WEKA Cluster status now available via AWS Lambda Function call presented in the Terraform outputs. Update “type”: “progress” to “type”: “status”
• Any protocol servers deployed by Terraform will now have their host names listed in output
• Backend instances will now update if the Automatic Scaling Group template is updated.

Important note:
We require now additional permissions for the lambda iam role:

• secretsmanager:PutSecretValue
• lambda:InvokeFunction

v1.0.13

• Updated WEKA default version to 4.2.12.87

v1.0.12

• Updated WEKA default version to 4.2.11

v1.0.11

• Updated WEKA default version to 4.2.12
• Ability to provision WEKA S3 protocol servers
• Added support for encrypted EBS using KMS key id
• Added support for providing get_weka_io_token from secrets manager
• Added support for utilizing all weka client instances network cards

v1.0.9

• Updated WEKA default version to 4.2.11.
• Fixed: smb protocol gws setup.
• Added region to output helper commands to support using provider with non default region.
• Added support for UDP mode for WEKA backends
• Added support to inject script to our backends init script.
• Update i3en.6xlarge default containers config.
• Added option to not configure key pair on EC2 instances for scenarios where policies forbid the use of key pair.
• Added support for detecting client architecture of official supported Arm clients.

v1.0.8

• 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 EC2 VM instances powered by AWS Graviton ARM based processors, and requires WEKA version 4.3.0 and above. See docs.weka.io for the full list of supported instances.
• Added auto scaling and auto healing capabilities for NFS protocol nodes.
• 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.
• “weka_username” variable is removed from the Terraform module as by default WEKA ‘admin’ username is used, and a password is generated by Terraform. Both the ‘admin’ username and password are stored in AWS Secrets Manager, to be used for communications between WEKA cluster and AWS, particularly during scale-out/in operations.
• Enhanced progress reporting as it relates to deployment and readiness of various WEKA cluster components.

v1.0.7

• Updated WEKA default version to 4.2.9.28