build(deps): Bump sigs.k8s.io/cluster-api-provider-aws/v2 from 2.7.1 to 2.8.1 in /hack/third-party/capa

[dependabot]

Bumps sigs.k8s.io/cluster-api-provider-aws/v2 from 2.7.1 to 2.8.1.

Release notes

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

v2.8.1

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

Documentation

There is no v2.8.0 GitHub release due to issues during the release process.

Changelog since v2.7.1

Urgent Upgrade Notes

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

• Action required Bump CAPI to v1.9.z !! ACTION REQUIRED BEFORE UPGRADING !! If you are using the AWSManagedControlPlane to provision EKS clusters and you do not have a spec.Version specified in such resource (meaning you are relying on the default that AWS provides), you will need to either: a) explicitly set such spec.Version field before upgrading CAPA or b) disable the MachineSetPreflightChecks in your cluster either: b1) by setting this core CAPI feature gate to false b2) or by disabling it via the relevant annotation on all the machineSets belonging to said cluster (follow this guide on how to do this: https://cluster-api.sigs.k8s.io/tasks/experimental-features/machineset-preflight-checks). This is necessary as core CAPI 1.9 introduces a feature gate change, setting MachineSetPreflightChecks=true, which in turn relies on the presence of spec.Version and status.Version on the AWSManagedControlPlane object. We are planning a future refactor of these API fields in v1beta3 (kubernetes-sigs/cluster-api-provider-aws#3853). Other places where you can find details on this are:
  • kubernetes-sigs/cluster-api-provider-aws#5225
  • kubernetes-sigs/cluster-api#11117
  • https://kubernetes.slack.com/archives/CD6U2V71N/p1739783013734149 (#5209, @​damdo)
• Action required From this release onwards we recommend not creating clusters using the classic ELB (which is the default for the API). Classic ELB support is deprected and support will be removed in a future version. For new & existing clusters that use a classic elb AND do not specify the health check protocol then the protocol will be changed/set to TCP instead of SSL. If you want to use a classic elb with an SSL healthcheck then you will need to specify the cipher suites to use in the KubeadmControlPlane:

apiVersion: controlplane.cluster.x-k8s.io/v1beta1
kind: KubeadmControlPlane
metadata:
  name: "${CLUSTER_NAME}-control-plane"
spec:
  kubeadmConfigSpec:
    clusterConfiguration:
      apiServer:
        extraArgs:
          cloud-provider: external
      # This is needed for Kubernetes v1.30+ since else it uses the Go defaults which don't
      # work with AWS classic load balancers, see
      # https://github.com/kubernetes-sigs/cluster-api-provider-aws/issues/5139. If you use
      # another load balancer type such as NLB, this is not needed.
      #
      # The list consists of the secure ciphers from Go 1.23.3, plus some less secure

</tr></table>

... (truncated)

Commits

• 49c75ac Merge pull request #5428 from damdo/bump-cloudbuild-gcb-image-go-1.23
• 468aa37 cloudbuild: bump gcb image to get go 1.23
• 29ef6c7 Merge pull request #5426 from mzazrivec/fix_doc_links
• dea4012 Merge pull request #5422 from nrb/retry-boskos-checkouts
• 6c93889 Merge pull request #5418 from richardcase/fix_efs_e2e_test
• 1e93dc7 Retry boskos account checkouts
• eb3ff6e refactor: remove old setup logic for AWSCluster
• b7fcdff fix: efs e2e test breaking
• 5b02ba0 Merge pull request #5425 from richardcase/5424_ensurepaused_fixed
• afcd118 Fix links to superseded document
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually 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)

[jimmidyson]

@dependabot rebase

[dependabot]

Looks like this PR has been edited by someone other than Dependabot. That means Dependabot can't rebase it - sorry!

If you're happy for Dependabot to recreate it from scratch, overwriting any edits, you can request @dependabot recreate.

[jimmidyson]

@dependabot recreate