Components Changelog

What​

• eks/actions-runner-controller
  • Support Runner Groups
  • Enable configuration of the webhook queue size limit
  • Change runner controller Docker image designation
• Add documentation on Runner Groups and Autoscaler configuration

Why​

• Enable separate access control to self-hosted runners
• For users that launch a large number of jobs in a short period of time, allow bigger queues to avoid losing jobs
• Maintainers recommend new tag format. ghcr.io has better rate limits than docker.io.

References​

• https://github.com/actions/actions-runner-controller/issues/2056

What​

• use cloud posse's template provider

Why​

• arm64
• also this provider was not pinned in versions.tf so that had to be fixed somehow

References​

• closes

What​

• upgrade aws-sso modules: permission_sets, sso_account_assignments, and sso_account_assignments_root

Why​

• upstream updates

What​

• Add datadog-synthetics component

Why​

• This component is responsible for provisioning Datadog synthetic tests

• Supports Datadog synthetics private locations

  • https://docs.datadoghq.com/getting_started/synthetics/private_location
  • https://docs.datadoghq.com/synthetics/private_locations

• Synthetic tests allow you to observe how your systems and applications are performing using simulated requests and actions from the AWS managed locations around the globe and to monitor internal endpoints from private locations

What​

• Updated the README with EKS cluster

Why​

The example stack is outdated. Add notes for Github OIDC and karpenter

References​

https://cloudposse.atlassian.net/browse/DEV-835

What​

• Added support for allowing spaces read access to all members
• Added a reference for allowing spaces write access to the "Developers" group

Why​

• Spacelift moved to Spaces Access Control

References​

• https://docs.spacelift.io/concepts/spaces/access-control

What​

• Update Readmes of many components from Refarch Docs

What​

• Copies some common providers to the mixins folder

Why​

• Have a central place where our common providers are held.

What​

• Added ArgoCD GitHub notification subscription

Why​

• To use synchronous deployment pattern

What​

• updates to waf module:
  • aws provider from ~> 4.0 to => 4.0
  • module cloudposse/waf/aws from 0.0.4 to 0.2.0
  • different recommended catalog entry

Why​

• suggested some updates before we start using waf module

What​

• While supporting EKS/ARC arm64, continue to deploy amd64 by default
• Make tolerations.value optional

Why​

• Majority of echosystem support is currently amd64
• tolerations.value is option in Kubernetes spec

References​

• Corrects issue which escaped review in

What​

Added arm64 support for eks/arc

Why​

when supporting both amd64 and arm64, we need to select the correct architecture

References​

https://github.com/cloudposse/infra-live/pull/265

What​

• Update account-map to output account information for aws-config script
• Output AWS profile name for root of credential chain

Why​

• Enable aws-config to output account IDs and to generate configuration for "AWS Extend Switch Roles" browser plugin
• Support multiple namespaces in a single infrastructure repo

What​

• Upstream latest datadog-agent and datadog-configuration updates

Why​

• datadog irsa role
• removing unused input vars
• default to public.ecr.aws images
• ignore deprecated default.auto.tfvars
• move datadog-agent to eks/ subfolder for consistency with other helm charts

References​

N/A

What​

• bumped ecr
• remove unnecssary variable

Why​

• ECR version update
• We shouldn't need to set root_account_tenant_name in providers
• Some Terraform docs are out-of-date

References​

• n/a

What​

• Adding vars for vpc module and sending them directly to module

References​

• https://github.com/cloudposse/terraform-aws-vpc/blob/master/variables.tf#L10-L44

What​

• allow gh oidc role to use privileged as option for reading tf backend

Why​

• If deploying GH OIDC with a component that needs to be applied with SuperAdmin (aws-teams) we need to set privileged here

References​

• https://cloudposse.slack.com/archives/C04N39YPVAS/p1679409325357119

What​

• Uses Datdaog Configuration as it's source of datadog variables
• Now supports enabled: false on a team to destroy it.

What​

• added eks view only policy

Why​

• Provided updates from recent contracts

References​

• https://github.com/cloudposse/refarch-scaffold/pull/99

What​

• Upgrade 'datadog-lambda-forwarder' component to v1.3.0

Why​

• Be able to forward Cloudwatch Events via components.

References​

• N/A