[network-driver]: Add multi-pool Resource IPAM operator cell#44081
Merged
pippolo84 merged 4 commits intocilium:feature/dra-driverfrom Feb 11, 2026
Merged
Conversation
6fed791 to
af806cb
Compare
63c1cd0 to
215ff6c
Compare
e16189e to
b61a52d
Compare
9bc91a5 to
0a1a482
Compare
b61a52d to
c66c7d9
Compare
Member
Author
|
/test |
d52bd7b to
80b7b0b
Compare
Member
Author
|
/test |
HadrienPatte
reviewed
Feb 4, 2026
80b7b0b to
e675d24
Compare
YutaroHayakawa
approved these changes
Feb 5, 2026
Member
YutaroHayakawa
left a comment
There was a problem hiding this comment.
k8s resource change looks good to me. Some non-blocking comments.
HadrienPatte
approved these changes
Feb 5, 2026
joamaki
requested changes
Feb 9, 2026
operator/pkg/networkdriver/ipam/testdata/dra-resource-ipam.txtar
Outdated
Show resolved
Hide resolved
e675d24 to
5a9955c
Compare
Member
Author
|
/test |
5a9955c to
014ae8f
Compare
Member
Author
|
/test |
69cee71 to
ffb12cc
Compare
In order to have separated files for CiliumPodIPPool and the upcoming CiliumResourceIPPool for DRA resources IPAM. Signed-off-by: Fabio Falzoi <fabio.falzoi@isovalent.com>
Signed-off-by: Fabio Falzoi <fabio.falzoi@isovalent.com>
DRA resources IPAM relies on this specific field in CiliumNode to keep track of the requested and allocated IP pools. Doing this allows to avoid any interference between pod IPAM and DRA resources IPAM. Signed-off-by: Fabio Falzoi <fabio.falzoi@isovalent.com>
Add the operator cell that manages the multi-pool controller for DRA resource IPAM. The implementation works in the same way of the pod IPAM counterpart, but it is specialized for DRA resources and isolated from the existing one. Signed-off-by: Fabio Falzoi <fabio.falzoi@isovalent.com>
014ae8f to
e0c14da
Compare
joamaki
approved these changes
Feb 11, 2026
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
6 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.
Multi-Pool Resource IPAM replicates the way Multi-Pool IPAM mode allocates IP addresses to pods, but specializes for DRA resources. When a pod with a ResourceClaim is scheduled on a node, the Cilium Network Driver is responsible for setting up the needed DRA resources to fulfill the claim. With Multi Pool Resource IPAM the claim can specify a pool (namely, a
CiliumResourceIPPoolobject) from which the IP address should be taken and assigned to the resource.An example of a ResouceClaim Spec where two dummy devices are requested, each with an IP address from a different pool is the following:
This PR adds the operator part of Multi-Pool Resource IPAM (for more details refer to the Cilium Network Driver CfP). Specifically, the operator watches CiliumResourceIPPools to keep track of all the pools available in the cluster and based on the addresses requests from each agent, it carves out CIDRs from the pools and reserve them for the requesting node, so that they can assign single IPs.
Depends on #44080Blocked on #44033