On Fri, Jun 3, 2022 at 3:30 PM Miguel Duarte de Mora Barroso <mdbarroso@redhat.com> wrote:
On Fri, Jun 3, 2022 at 2:57 PM Felix Enrique Llorente Pastora <ellorent@redhat.com> wrote:On Fri, Jun 3, 2022 at 2:15 PM Fabian Deutsch <fdeutsch@redhat.com> wrote:Hey Felix,are you saying this will be providing IPAM to node NICs or to secondary NICs of pods (and VMs)?This is for node primary and secondary NICs.I think this proposal is to provide IPAM to interfaces *exclusively* on the nodes. For pods, you'd use an IPAM CNI plugin.
Yes, it means just node NICs, not pods.
On Fri, Jun 3, 2022 at 12:54 PM Felix Enrique Llorente Pastora <ellorent@redhat.com> wrote:Hi,--As an effort to implement an IPAM like feature for kubernetes cluster node we (the kubevirt network team) has put in place a design doc to extend kubernetes-nmstate to implement it, it also has some points related to adapt it to bare metal IPI.Basically it extends the "capture" feature to make reference to a new CRD NodeIPPool that will store the IPAM information. https://github.com/nmstate/kubernetes-nmstate/pull/1088Reviews are welcome.BR--Quique LlorenteCNV networking Senior Software Engineer
You received this message because you are subscribed to the Google Groups "kubevirt-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to kubevirt-dev+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/kubevirt-dev/CAHVoYmJQAc%3DmaoSDqQwWF%2BrEncCTQ6WVhYO_%2BNumJiStaTHuzA%40mail.gmail.com.
--Quique LlorenteCNV networking Senior Software Engineer
