Deleted vnet removed from ipam #247
-
We are using 3.0 version Azure ipam. Very happy with it, great tool. We currently see entries removed from the block when vnet resources are deleted in Azure. The reservation gets removed when the vnet is created. But when the vnet is deleted later the entry is removed completely removed from ipam and the cidr get assigned again to new reservation. I've seen discussions here that this could be influenced by a setting. I really want to delete the entry from ipam manually. |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 4 replies
-
Hi @janinternet, thank you for reaching out! Just to clarify, are you asking for the history of the Reservation to be completely removed, or something else? |
Beta Was this translation helpful? Give feedback.
-
Thank you for the quick answer. No, not the reservation. We don't want the association to the block to be removed automatically. When we delete the vnet from Azure the cidr is completely removed from ipam and the cidr is made available again. When we delete the vnet we would like to keep this cidr blocked in ipam so it will not get assigned again until we remove it manually. |
Beta Was this translation helpful? Give feedback.
That's a completely valid ask @janinternet. I'll add this to my near-term roadmap and keep you posted once I have something implemented so you can test & provide some feedback.
Thanks for the great suggestion!