whereabouts icon indicating copy to clipboard operation
whereabouts copied to clipboard

[Bug/Feature request] IP addresses does not persist on KubeVirt VMIs after restart

Open saffronjam opened this issue 5 months ago • 3 comments

Hello! We've been trying out whereabouts for our VM management using KubeVirt and it has worked great so far.

However, we've noticed that restarts to KubeVirt VMI's seems to release the IP address, even though the VM is very much still there. We also know that we are not the only one asking for this behavior.

We are using kubemacpool to ensure VMs get their unique MAC address that persist, but this IP management seems to not work the same way.

So, we are not sure if this is a bug or a feature request, or just "help wanted", hence the loose style of this issue. And we ask for some pointers in how we can ensure sticky IP address assignment to VMs from a pool.

System info

Whereabouts version: 0.8.0 (latest as of writing this) Kubernetes version: 1.30.3 KubeVirt version: 1.3.1

Config

{
  "cniVersion": "0.3.1",
  "name": "host-network-bridge",
  "type": "bridge",
  "bridge": "br0",
  "ipam": {
    "type": "whereabouts",
    "range": "192.168.100.2-192.168.100.254/24",
    "gateway": "192.168.100.1",
    "routes": [
      {
        "dst": "0.0.0.0/0",
        "gw": "192.168.100.1"
      }
    ],
    "dns": {
      "nameservers": [
        "8.8.8.8",
        "8.8.4.4"
      ]
    }
  }
}

Reproduce

  1. Create 10 KubeVirt VMs
  2. Note IPs
  3. Restart all VMs
  4. See that VMIs does not have the same IP (unless coincidence)

Thanks!

saffronjam avatar Aug 30 '24 08:08 saffronjam