-
Notifications
You must be signed in to change notification settings - Fork 8
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
reclaim of static ip #28
base: master
Are you sure you want to change the base?
reclaim of static ip #28
Conversation
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: acraghav The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Welcome @acraghav! It looks like this is your first PR to spectrocloud/cluster-api-provider-vsphere-static-ip 🎉 |
Hi @acraghav. Thanks for your PR. I'm waiting for a spectrocloud member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. 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. |
@acraghav , thanks for the PR ! There might be a simpler way of deallocating. If the IPClaims have the correct ownerRef, then we should be able to start from the owner and list the descendant IPClaims. Deleting these IPClaims should delete the corresponding IPAddresses. Currently, there seems to be a timing issue with the vsphereCluster ownerRef. Let me fix that and open a PR. |
@acraghav , I fixed the owner ref issue. Please try with the latest. Deleting VSphereCluster/VSphereMachine should result in the corresponding IPClaim being garbage collected. |
Implementation of reconciledelete to reclaim static ip.
Closes #27