Components Changelog

What​

• Updated the title

Why​

• It was an extra helping of copy/pasta

References​

What​

• Update Datadog components:
  • eks/datadog-agent see eks/datadog-agent/CHANGELOG.md
  • datadog-configuration better handling of enabled = false
  • datadog-integration move "module count" back to "module" for better compatibility and maintainability, see datadog-integration/CHANGELOG.md
  • datadog-lambda-forwared fix issues around enable = false and incomplete destruction of resources (particularly log groups) see datadog-lambda-forwarder/CHANGELOG.md
  • Cleanup datadog-monitor see datadog-monitor/CHANGELOG.md for details. Possible breaking change in that several inputs have been removed, but they were previously ignored anyway, so no infrastructure change should result from you simply removing any inputs you had for the removed inputs.
  • Update datadog-sythetics dependency remote-state version
  • datadog-synthetics-private-location migrate control of namespace to helm-release module. Possible destruction and recreation of component on upgrade. See CHANGELOG.md

Why​

• More reliable deployments, especially when destroying or disabling them
• Bug fixes and new features

What:​

• Updated modules/spacelift/worker-pool from 0.34.2 to 0.35.1 and adapted new variable features
• Updated modules/bastion from 0.35.0 to 0.35.1
• Updated modules/github-runners from 0.35.0 to 0.35.1

Why:​

• Modules were utilizing previous ec2-autoscale-group versions

References:​

• terraform-aws-ec2-autoscale-group
• Terraform Registry

What​

• [eks/karpenter] use Instance Profile name from EKS output
• Clarify recommendation and fix defaults regarding deploying add-ons to managed node group

Why​

• Bug fix: Karpenter did not work when legacy mode disabled
• Originally we expected to use Karpenter-only clusters and the documentation and defaults aligned with this. Now we recommend all Add-Ons be deployed to a managed node group, but the defaults and documentation did not reflect this.

What​

• Upsteam the latest ecs-service component

Why​

• Support ecspresso deployments
• Support s3 task definition mirroring
• Support external ALB/NLN components

What​

• moved changelog for individual components
• changed title

Why​

• Title changelogs consistently by components version
• Separate changes by affected components

References​

• https://github.com/cloudposse/knowledge-base/discussions/132

What​

• Fix eks/cluster node_group_defaults to default to legal (empty) values for kubernetes_labels and kubernetes_taints
• Increase eks/cluster managed node group default disk size from 20 to 50 GB

Why​

• Default values should be legal values or else they are not really defaults
• Nodes were running out of disk space just hosting daemon set pods at 20 GB

Why:​

• cloudposse/ssm-parameter-store/aws was out of date
• There are no new changes incorporated but just wanted to standardize new modules to updated version

What:​

• Updated the following to v0.11.0:

0.10.0 modules/argocd-repo
0.10.0 modules/aurora-mysql
0.10.0 modules/aurora-postgres
0.10.0 modules/datadog-configuration
0.10.0 modules/eks/platform
0.10.0 modules/opsgenie-team/modules/integration
0.10.0 modules/ses
0.9.1 modules/datadog-integration

What​

• revert some changes to argocd component
• connect argocd notifications with ssm secrets
• remove deployment_id from argocd-repo component
• correct app_hostname since gha usually adds protocol

Why​

• regressions with argocd notifications caused github actions to timeout
• deployment_id no longer needed for fascilitating communication between gha and ArgoCD
• application urls were incorrect and problematic during troubleshooting

What​

• Added the component eks/keda

Why​

• We've deployed KEDA for a few customers now and the component should be upstreamed

References​

• n/a

What​

• Added deletion_protection for cognito
• Added options for dedicated master for elasticsearch

Why​

• Allow the default options to be customized

References​

• Customer requested additions

What​

• Set the version to the correct updated release

Why​

• Needs to match correct version

References​

What​

• Upgraded tgw components to support cross region connections
• Added back tgw/cross-region-hub-connector with overhaul to support updated tgw/hub component

Why​

• Deploy tgw/cross-region-hub-connector to create peered TGW hubs
• Use tgw/hub both for in region and intra region connections

References​

• n/a

What​

• Proper handling of cold start and enabled=false

Why​

• Fixes
• Supersedes and closes
• Cloud Posse standard requires error-free operation and no resources created when enabled is false, but previously this component had several errors

What:​

• Added enabled parameter for modules/aws-saml/modules/okta-user/main.tf and modules/datadog-private-location-ecs/main.tf

Why:​

• No support for disabling the creation of the resources

What:​

• Updated bastion, redshift, rds, spacelift, and vpc to utilize the newest version of cloudposse/security-group/aws

Why:​

• cloudposse/security-group/aws components were not updated to 2.2.0

References:​

• AWS Security Group Component

What​

• update descriptions *_account_account_name variables
  • I replaced stage with short because that is the description used for the respective outputs entries

Why​

• to help future implementors of CloudPosse's architectures

References​

• n/a

What​

• update usage snippet in readme for eks/cluster component

Why​

• fix incorrect shape for one of the items in aws_team_roles_rbac
• improve consistency
• remove variables that are not appliable for the component

References​

• n/a

What​

• filter out “SUSPENDED” accounts (aka accounts in waiting period for termination) for account-map component

Why​

• suspended account cannot be used, so therefore it should not exist in the account-map
• allows for new active accounts with same exact name of suspended account to exists and work with account-map

References​

• n/a

What​

• Adding Karpenter troubleshooting to readme
• Adding https://endoflife.date/amazon-eks to EKS/Cluster

References​

• https://karpenter.sh/docs/troubleshooting/
• https://endoflife.date/amazon-eks