Bump sigs.k8s.io/cluster-api-provider-aws/v2 from 2.0.2 to 2.3.4

[dependabot[bot]]

Bumps sigs.k8s.io/cluster-api-provider-aws/v2 from 2.0.2 to 2.3.4.

Release notes

Sourced from sigs.k8s.io/cluster-api-provider-aws/v2's releases.

v2.3.1

Release notes for Cluster API Provider AWS (CAPA) v2.3.1

Documentation

Changelog since v2.3.0

NOTE: This release updates the default cluster template to use the external cloud provider which is deployed using CRS. You will need to enable the CRS.

Changes by Kind

Uncategorized

• Resolved issue where deleted control planes were still registered in the kube-apiserver load balancer, causing potential disruptions. (#4704, @​k8s-infra-cherrypick-robot)
• Skip instance refresh attempt if ASG does not yet exist (#4698, @​AndiDog)
• Updated the default clusterctl template to use external cloud-controller-manager (#4695, @​k8s-infra-cherrypick-robot)
• Use seedling emoji for dependabot pull requests (#4652, @​kranurag7)

The image for this release is: registry.k8s.io/cluster-api-aws/cluster-api-aws-controller:v2.3.1

Thanks to all our contributors.

Dependencies

Added

Nothing has changed.

Changed

Nothing has changed.

Removed

Nothing has changed.

v2.3.0

Release notes for Cluster API Provider AWS (CAPA) v2.3.0

Documentation

Changelog since v2.2.4

Urgent Upgrade Notes

(No, really, you MUST read this before you upgrade)

• If you're using the S3 bucket functionality, the following permissions are required for the VPCEndpoint to be managed ec2:CreateVpcEndpoint, ec2:ModifyVpcEndpoint, ec2:DeleteVpcEndpoints, ec2:DescribeVpcEndpoints. Rerun clusterawsadm to update IAM permissions, or update it manually. (#4577, @​vincepri)
• When the VPC is managed, the SubnetSpec.ID field can be used now to offload subnet management to the AWSCluster controller. The id should be set to a string that DOES NOT start with subnet-; the value is used to set the Name tag in the subnet resource and the actual AWS resource ID is stored in SubnetSpec.ResourceID. (#4474, @​vincepri)

... (truncated)

Commits

• See full diff in compare view

You can trigger a rebase of this PR by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Note Automatic rebases have been disabled on this pull request as it has been open for over 30 days.