The memcached version now sets the default version to 1.5.16. We were using 1.4.24 before, but that's no longer supported. If you wish to use a different version, use the memcached_version input variable.
The redis module now sets the default version to 5.0.5. We were using 2.8.24 before, but that's now quite out of date. If you wish to use a different version, use the redis_version input variable.
The go environment setup scripts have been updated with go modules support. As a part of this, glide is no longer supported. Note that you will need to update the flags to continue use with dep. Refer to the migration guide below for more details.
This release consolidates ecs-service-with-alb, ecs-service-with-discovery, ecs-service, and ecs-fargate into one module. As a part of this, features that were only available in one of the flavors are now available in all flavors. Users of the old modules will see the following feature enhancements:
You can now set up an App AutoScaling Target in all flavors, which will allow you to configure AutoScaling Policies on the ECS Service. Previously this was not available in ecs-service.
You can now fully setup the awsvpc network mode in all flavors. Specifically, the subnets and security groups of the ECS task are now configurable. Previously this was only available on ecs-fargate and ecs-service-with-discovery.
You can now setup a canary deployment in all flavors. Previously this was only available on ecs-service and ecs-service-with-alb.
You can now attach volumes on your ECS tasks in all flavors. Previously this was not available in ecs-service-with-discovery.
Add support for slow start to ecs-service-with-alb. You can set a delay in seconds (using input variable alb_slow_start) that controls how long the load balancer should wait before starting to send requests to the targets.
EC2 based ECS clusters will now use gp2 as the root volume. If you would like the old behavior (e.g to avoid a redeploy), you can set cluster_instance_root_volume_type to standard.
This release introduces support for Kubernetes cluster-autoscaler, a Kubernetes application that manages autoscaling for your EKS cluster workers. This can be used to automatically scale up or down your worker pools based on demand from Pods.
Check out the updated README for instructions on how to setup the cluster autoscaler for your worker pools.
Fix a bug with the eks-alb-ingress-controller module where you could end up with a perpetual diff in the plan.
Fix a regression bug with eks-cluster-control-plane where it returned the information on the EKS cluster before the API came up (as checked by null_resource.wait_for_api). This could lead to issues in your terraform code if you were chaining an API request immediately following the creation of the EKS cluster.
This release exposes the ability to tag the EKS cluster using the custom_tags_eks_cluster input variable on eks-cluster-control-plane. Note that you will need to be using AWS provider version >=2.31.0.
This release fixes an issue that was introduced in Terraform version 0.12.11 in which indexed references to null resources cause an error. The issue is described in detail in hashicorp/terraform#23140. The change is backwards compatible with earlier revisions of TF 0.12.
This alpha release bumps the version of Go used with ssh-grunt from 1.11 to 1.13.3 to address an issue with long delays under certain (mysterious) conditions. We'll confirm the fix before releasing v0.20.1.
This release bumps the version of Go used with ssh-grunt from 1.11 to 1.13.3 to address an issue with long delays under certain (mysterious) conditions. This build was tested successfully as v0.20.1-alpha.1.
The recently-created custom-iam-group module has been renamed to custom-iam-entity. The new module has support for creating roles in addition to groups.
The saml-iam-roles and cross-account-iam-roles modules now support tags. Use a map of tags to create tagged roles. For example:
tags = { Department = "IT" Environment = "Production" }
In v0.18.6, we introduced the iam-admin policy for IAM groups. The policy allows administration of IAM without full administrator privileges. This update extends the iam-admin to work with SAML and cross-account roles for users that do not use IAM groups.
This release addresses an issue where the transaction logs are stored on an EBS volumes but the data is not. If autoscaling deletes a node, the snapshots in the data volume are lost. The only fix then is to rm the transaction-logs/version-2 directory and restart zookeeper, allowing it to sync from the other nodes in the ensemble.
With this fix, data is stored on a separate EBS volume. If the node is terminated, the volume is reattached to a new node, and the data will remain intact.
Fixes a regression bug introduced in k8s-namespace and k8s-namespace-roles with the behavior of create_resources. Starting with terraform v0.12.11, referencing resource index 0 of those that were not created with count = 0 is an error where as before it was null. This means that we need to add a conditional for referencing those resources to only index into it when count > 0.
This release also adds the create_resources parameter to k8s-service-account.