Not supporting Kubernetes 1.31 onwards

[hsmade]

Since #5195 was closed, no new release was cut.
This means Kubernetes version 1.31 and onwards can't be used with CAPA.
Can we please get a new release to make this work?

[k8s-ci-robot]

This issue is currently awaiting triage.

If CAPA/CAPI contributors determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[damdo]

Hey @hsmade, yes, we are planning on supporting k8s 1.31

At the moment we are blocked on two things to make it work and create a CAPA 2.8 release that supports it:

• 🌱 Bump CAPI to v1.9.z #5209 (blocked by ELB health check fails with Kubernetes >=v1.30.x #5139)
• ELB health check fails with Kubernetes >=v1.30.x #5139 (which we are trying to find a solution for)

[richardcase]

/milestone v2.8

[mloiseleur]

As a workaround, CAPA works on 1.31 with this small kustomization patch:

  - patch: |-
      - op: remove
        path: /spec/conversion/webhook/clientConfig/caBundle
    target:
      kind: CustomResourceDefinition
      name: awsclustercontrolleridentities.infrastructure.cluster.x-k8s.io|awsclusterroleidentities.infrastructure.cluster.x-k8s.io|awsclusters.infrastructure.cluster.x-k8s.io|awsclustertemplates.infrastructure.cluster.x-k8s.io|awsmachines.infrastructure.cluster.x-k8s.io|awsmachinetemplates.infrastructure.cluster.x-k8s.io|awsmanagedcontrolplanes.controlplane.cluster.x-k8s.io|eksconfigs.bootstrap.cluster.x-k8s.io|eksconfigtemplates.bootstrap.cluster.x-k8s.io

[hsmade]

But that doesn't help if you use the capi-operator, or?