Tags defined in subnet spec should be applied

giantswarm · Jan 21, 2025 · 90bc60f · 90bc60f
1 parent dc05849
commit 90bc60f
Show file tree

Hide file tree

Showing 2 changed files with 6 additions and 1 deletion.
diff --git a/CHANGELOG.md b/CHANGELOG.md
@@ -7,6 +7,10 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+### Fixed
+
+- Tags defined in subnet spec should be applied to the subnet resource on AWS.
+
 ## [2.26.0] - 2024-12-05
 
 ### Added

diff --git a/helm/cluster-api-provider-aws/values.yaml b/helm/cluster-api-provider-aws/values.yaml
@@ -9,7 +9,8 @@ name: cluster-api-provider-aws
 #   * S3 user data support for AWSMachinePools (https://github.com/giantswarm/cluster-api-provider-aws/pull/607/commits/905c44ab2afde5e2d4e983066ab9856859a0de47)
 #   * Filter out AWS internal tags when reconciling (https://github.com/kubernetes-sigs/cluster-api-provider-aws/pull/5181/commits/4c61f2b5a01e0b67e647868a066dda1947b97d4c)
 #   * Support EC2 lifecycle hooks for machine pools (https://github.com/giantswarm/cluster-api-provider-aws/pull/613)
-tag: v2.7.1-gs-09d96748c
+#   * Tags defined in subnet spec should be applied (https://github.com/giantswarm/cluster-api-provider-aws/pull/615)
+tag: v2.7.1-gs-5ffc044f4
 
 registry:
   domain: gsoci.azurecr.io