Cannot create IPAddressClaim due to webhook after introducing v1beta1

[mcbenjemaa]

What steps did you take and what happened?

I wanted to create an IPAddressClaim

---
apiVersion: ipam.cluster.x-k8s.io/v1beta1
kind: IPAddressClaim
metadata:
  name: my-claim
spec:
  poolRef:
    apiGroup: ipam.cluster.x-k8s.io
    kind: InClusterIPPool
    name: inclusterippool-sample

But this failed,

Error from server (InternalError): error when creating "examples/ipam/ip-addr-claim.yaml": Internal error occurred: failed calling webhook "validation.ipaddressclaim.ipam.cluster.x-k8s.io": failed to call webhook: the server could not find the requested resource

and neither v1alpha1 works

What did you expect to happen?

IPAddressClaim created

Cluster API version

v1.6

Kubernetes version

v1.28.4

Anything else you would like to add?

No response

Label(s) to be applied

/kind bug
One or more /area label. See https://github.com/kubernetes-sigs/cluster-api/labels?q=area for the list of labels.

[k8s-ci-robot]

This issue is currently awaiting triage.

If 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/test-infra repository.

[mcbenjemaa]

Seems: #9861

[sbueringer]

Yup. Already fixed and cherry-picked

[mcbenjemaa]

@sbueringer, but the v1.6 manifests don't sound correct.

yeah, the fix will be released into the upcoming release.

[sbueringer]

/close

Given there's nothing more we can do apart from waiting for the release

[k8s-ci-robot]

@sbueringer: Closing this issue.

In response to this:

/close

Given there's nothing more we can do apart from waiting for the release

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/test-infra repository.