ipam: Support for static IP allocation in Azure#42219
Merged
qmonnet merged 1 commit intocilium:mainfrom Oct 22, 2025
Merged
Conversation
Contributor
Author
|
/test |
qmonnet
requested changes
Oct 17, 2025
Member
qmonnet
left a comment
There was a problem hiding this comment.
Thanks! I just looked at the docs - can you please use the .. code-block directive with the relevant language for your snippets? Looks good otherwise.
pippolo84
reviewed
Oct 17, 2025
Member
pippolo84
left a comment
There was a problem hiding this comment.
Thanks! Overall LGTM, left a couple of questions and a suggestion inline.
fdebee1 to
c4460ef
Compare
Contributor
Author
|
/test |
qmonnet
approved these changes
Oct 20, 2025
Member
qmonnet
left a comment
There was a problem hiding this comment.
Doc change looks good, thank you!
This commit implements the AllocateStaticIP logic in the Azure Operator. The Operator is now able to assign IPs from tagged Public IP Prefixes to standalone VM instances and VMSS instances. Signed-off-by: Anton Ippolitov <anton.ippolitov@datadoghq.com>
c4460ef to
5c035c2
Compare
Contributor
Author
|
/test |
tamilmani1989
approved these changes
Oct 22, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
This PR implements Public IP assignments functionality for Azure, it's exactly the same idea as #34622 for AWS.
This implementation relies on tagged Azure Public IP Prefixes. Users can specify Public IP Prefix tags in their CNI config and the Operator will automatically assign to the node a Public IP from a Prefix which matches.
The implementation works for both VMSS instances and standalone VM instances.
Testing
Backported to our 1.18.2 fork. Then created an Azure VMSS node in a public subnet (no NAT gateway). Set
static-ip-tagsin the CNI config for this node:Afterwards, created an Azure Public IP Prefix with tags
pool-name=anton-test. Then confirmed:When masquerading was enabled (thanks to Azure: add support for masquerading #42196), the pod was able to use that Public IP:
When the instance was deleted, the IP was released