mirror of
https://github.com/ysoftdevs/terraform-aws-eks.git
synced 2026-03-17 23:13:46 +01:00
14 KiB
14 KiB
Change Log
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog and this project adheres to Semantic Versioning.
Unreleased
v13.1.0 - 2020-11-02
FEATURES:
- Add Launch Template support for Managed Node Groups (#997)
- Add
cloudwatch_log_group_arnto outputs (#1071) - Add kubernetes standard labels to avoid manual mistakes on the managed
aws-authconfigmap (#989)
CI:
- Use ubuntu-latest instead of MacOS for docs checks (#1074)
- Fix GitHub Actions CI macOS build errors (#1065)
BUG FIXES:
- The type of the output
cloudwatch_log_group_nameshould be a string instead of a list of strings (#1061) - Use splat syntax to avoid errors during destroy with an empty state (#1041)
- Fix cycle error during the destroy phase when we change workers order (#1043)
- Set IAM Path for
cluster_elb_sl_role_creationIAM policy (#1045) - Use the amazon
ImageOwnerAliasfor worker ami owner instead of owner id (#1038)
NOTES:
- Managed Node Groups now support Launch Templates. The Launch Template it self is not managed by this module, so you have to create it by your self and pass it's id to this module. See docs and
examples/launch_templates_with_managed_node_groups/for more details. - The output
cloudwatch_log_group_namewas incorrectly returning the log group name as a list of strings. As a workaround, people were usingmodule.eks_cluster.cloudwatch_log_group_name[0]but that was totally inconsistent with output name. Those users can now usemodule.eks_cluster.cloudwatch_log_group_namedirectly. - Keep in mind that changing the order of workers group is a destructive operation. All workers group are destroyed and recreated. If you want to do this safely, you should move then in state with
terraform state mvuntil we manage workers groups as maps.
v13.0.0 - 2020-10-06
BUG FIXES:
- Use customer managed policy instead of inline policy for
cluster_elb_sl_role_creation(#1039) - More compatibility fixes for Terraform v0.13 and aws v3 (#976)
- Create
cluster_private_accesssecurity group rules when it should (#981) - random_pet with LT workers under 0.13.0 (#940)
ENHANCEMENTS:
- Make the
cpu_creditsoptional for workers launch template (#1030) - update the
wait_for_cluster_cmdlogic to usecurlifwgetdoesn't exist (#1002)
FEATURES:
- Add
load_balancersparameter to associate a CLB (Classic Load Balancer) to worker groups ASG (#992) - Dynamic Partition for IRSA to support AWS-CN Deployments (#1028)
- Add AmazonEKSVPCResourceController to cluster policy to be able to set AWS Security Groups for pod (#1011)
- Cluster version is now a required variable. (#972)
CI:
- Bump terraform pre-commit hook version and re-run terraform-docs with the latest version to fix the CI (#1033)
- fix CI lint job (#973)
DOCS:
- Add important notes about the retry logic and the
wgetrequirement (#999) - Update README about
cluster_versionvariable requirement (#988) - Mixed spot + on-demand instance documentation (#967)
- Describe key_name is about AWS EC2 key pairs (#970)
- Better documentation of
cluster_idoutput blocking (#955)
BREAKING CHANGES:
- Default for
cluster_endpoint_private_access_cidrsis nownullinstead of["0.0.0.0/0"]. It makes the variable required whencluster_create_endpoint_private_access_sg_ruleis set totrue. This will force everyone who want to have a private access to set explicitly their allowed subnets for the sake of the principle of least access by default. cluster_versionvariable is now required.
NOTES:
credit_specificationfor worker groups launch template can now be set tonullso that we can use non burstable EC2 families- Starting in v12.1.0 the
cluster_idoutput depends on thewait_for_clusternull resource. This means that initialisation of the kubernetes provider will be blocked until the cluster is really ready, if the module is set to manage the aws_auth ConfigMap and user followed the typical Usage Example. kubernetes resources in the same plan do not need to depend on anything explicitly.
v12.2.0 - 2020-07-13
DOCS:
- Update required IAM permissions list (#936)
- Improve FAQ on how to deploy from Windows (#927)
- autoscaler X.Y version must match (#928)
FEATURES:
- IMDSv2 metadata configuration in Launch Templates (#938)
- worker launch templates and configurations depend on security group rules and IAM policies (#933)
- Add IAM permissions for ELB svc-linked role creation by EKS cluster (#902)
- Add a homemade
depends_onfor MNG submodule to ensure ordering of resource creation (#867)
BUG FIXES:
- Strip user Name tag from asg_tags #946)
- Get
on_demand_allocation_strategyfromlocal.workers_group_defaultswhen deciding to usemixed_instances_policy(#908) - remove unnecessary conditional in private access security group (#915)
NOTES:
- Addition of the IMDSv2 metadata configuration block to Launch Templates will cause a diff to be generated for existing Launch Templates on first Terraform apply. The defaults match existing behaviour.
v12.1.0 - 2020-06-06
FEATURES:
- Add aws_security_group_rule.cluster_https_worker_ingress to output values (#901)
- Allow communication between pods on workers and pods using the primary cluster security group (optional) (#892)
BUG FIXES:
- Revert removal of templates provider (#883)
- Ensure kubeconfig ends with \n (#880)
- Work around path bug in aws-iam-authenticator (#894)
DOCS:
- Update FAQ (#891)
NOTES:
- New variable
worker_create_cluster_primary_security_group_rulesto allow communication between pods on workers and pods using the primary cluster security group (Managed Node Groups or Fargate). It defaults tofalseto avoid potential conflicts with existing security group rules users may have implemented.
v12.0.0 - 2020-05-09
BUG FIXES:
- Fix Launch Templates error with aws 2.61.0 (#875)
- Use splat syntax for cluster name to avoid
(known after apply)in managed node groups (#868)
DOCS:
FEATURES:
ENHANCEMENTS:
- Remove dependency on external template provider (#854)
BREAKING CHANGES:
- The default
cluster_versionis now 1.16. Kubernetes 1.16 includes a number of deprecated API removals, and you need to ensure your applications and add ons are updated, or workloads could fail after the upgrade is complete. For more information on the API removals, see the Kubernetes blog post. For action you may need to take before upgrading, see the steps in the EKS documentation. Please set explicitly yourcluster_versionto an older EKS version until your workloads are ready for Kubernetes 1.16.
v11.1.0 - 2020-04-23
BUG FIXES:
- Add
vpc_config.cluster_security_groupoutput as primary cluster security group id (#828) - Wrap
local.configmap_roles.groupswith tolist() to avoid panic (#846) - Prevent
coalescelistnull argument error when destroying worker_group_launch_templates (#842)
FEATURES:
- Add support for EC2 principal in assume worker role policy for China (#827)
v11.0.0 - 2020-03-31
FEATURES:
- Add instance tag specifications to Launch Template (#822)
- Add support for additional volumes in launch templates and launch configurations (#800)
- Add interpreter option to
wait_for_cluster_cmd(#795)
ENHANCEMENTS:
- Use
aws_partitionto build IAM policy ARNs (#820) - Generate
aws-authconfigmap's roles from Object. No more string concat. (#790) - Add timeout to default wait_for_cluster_cmd (#791)
- automate changelog management (#786)
BUG FIXES:
- Fix destroy failure when talking to EKS endpoint on private network (#815)
- add ip address when manage_aws_auth is true and public_access is false (#745)
- Add node_group direct dependency on eks_cluster (#796)
- Do not recreate cluster when no SG given (#798)
- Create
falseand avoid waiting forever for a non-existent cluster to respond (#789) - fix git-chglog template to format changelog
Typenicely (#803) - fix git-chglog configuration (#802)
CI:
- Restrict sementic PR to validate PR title only (#804)
TESTS:
- remove unused kitchen test related stuff (#787)