Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

IPAM webhooks are not working #9860

Closed
schrej opened this issue Dec 12, 2023 · 1 comment · Fixed by #9861
Closed

IPAM webhooks are not working #9860

schrej opened this issue Dec 12, 2023 · 1 comment · Fixed by #9861
Assignees
Labels
area/ipam Issues or PRs related to ipam kind/bug Categorizes issue or PR as related to a bug. triage/accepted Indicates an issue or PR is ready to be actively worked on.

Comments

@schrej
Copy link
Member

schrej commented Dec 12, 2023

What steps did you take and what happened?

Attempt to create an IPAddressClaim or an IPAddress resource. The creation will fail with a resource not found error as the webhook implementation expects v1beta1 resources, but the webhook configuration still uses v1alpha1.

What did you expect to happen?

The validating Webhooks accept a valid resource.

Cluster API version

since 1.6.0
tested with 2575fa5

Kubernetes version

No response

Anything else you would like to add?

No response

Label(s) to be applied

/kind bug
/area ipam
/assign

@k8s-ci-robot k8s-ci-robot added kind/bug Categorizes issue or PR as related to a bug. area/ipam Issues or PRs related to ipam needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Dec 12, 2023
@sbueringer
Copy link
Member

/triage accepted

@k8s-ci-robot k8s-ci-robot added triage/accepted Indicates an issue or PR is ready to be actively worked on. and removed needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Dec 12, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/ipam Issues or PRs related to ipam kind/bug Categorizes issue or PR as related to a bug. triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants