-
Notifications
You must be signed in to change notification settings - Fork 24
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
Ensure IPAddress has a ClusterName label as CAPI resources #220
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
I would really like to merge #203 before this, and then add this change there though. I'm still looking for some feedback on it, but rikatz hasn't gotten around to it yet.
Let me know if you'd like to have this right away. If someone else is available to take a look at #203 I'd of course appreciate that as well!
/remove-approve Somewhat unintuitive 😄 |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: schrej, zhanggbj The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
@schrej thanks for your review! No rush, but it would be great to merge this small change If everything works fine. |
@zhanggbj IIRC you can trigger the tests directly back on pipelines... Or...let's see if prow is smart: /retest |
We've merged #203 now. Could you adapt your PR? I think it makes sense to move this into the generic reconciler, probably around here: https://github.com/kubernetes-sigs/cluster-api-ipam-provider-in-cluster/blob/main/pkg/ipamutil/reconciler.go#L210 |
Signed-off-by: Gong Zhang <gongz@vmware.com>
I finally figured out why the test is failing:
Can you create the cluster you're referencing during that test to avoid reconciliation to be skipped? |
/lgtm |
@schrej Thank you for fixing the test! I just came back from a vacation. |
What this PR does / why we need it:
CAPI has a contract to label all created resources with a ClusterName label. CAPV will label IPAddressClaim. This PR is to ensure IPAddress also got one.
Please find more discussion in kubernetes-sigs/cluster-api-provider-vsphere#2218
Which issue(s) this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)
format, will close the issue(s) when PR gets merged):Fixes #