Miguel Duarte Barroso

BTW: you should rebase this with latest master. It will fix the unit test issue you're currently facing, and give us results.

> Fix for #198 > > This solves many logging issues we've had with whereabouts and the ip-reconciler. We already have this working on our custom whereabouts fork we use...

Same as #269 .

> from one of the Nodes that I got OOM. what can increase the Memory like that ? I'm unsure, but, we're still using the requests / limits of when...

I'm unsure this is working ... This PR features a change to `.github/workflows/test.yml` and somehow, the tests are **not** being executed. According to the [build logs](https://github.com/k8snetworkplumbingwg/whereabouts/runs/7915060589?check_suite_focus=true#step:5:65), "No changes found".

I'm an idiot, I'm using the wrong action, `verify-changed-files` is meant to: > verify file changes that occur during the workflow execution. ... which is really not what I'm looking...

I think the best option available for having a static IP address on a pod is to use the [static IPAM plugin](https://www.cni.dev/plugins/current/ipam/static/). Why do you need to use whereabouts for...

> # Test for IPv4/IPv6 dual-stack along with Old Range configuration > ## NAD > ``` > apiVersion: "k8s.cni.cncf.io/v1" > kind: NetworkAttachmentDefinition > metadata: > name: whereabouts-conf > spec: >...

> @maiqueb Thank you so much for your review :) > > I intended to rewrite the history properly once I got review for the overall structure of the code,...

We would welcome you in the [network plumbing work group bi-monthly call](https://github.com/k8snetworkplumbingwg/community#meetings) to discuss this use case. If the community accepts this feature request, we can then add a project...