Netplan lacks VXLAN support

[klockren]

With ifupdown, we configured VXLAN:s via post-up scripts.

Netplan should have VXLAN configuration directives built-in!

vxlans:
  vx5522:
    id: 5522
    ttl: 10
    multicast-group: 239.0.0.10
    port: 4789
    link: eno1
    mtu: 1554
    addresses: [ "10.3.98.5/24" ]
    nameservers:
      addresses: [ "127.0.0.1" ]
      search: [ domain1.example.com, domain2.example.com ]
  vx339:
    id: 339
    ttl: 1
    multicast-group: 239.0.0.39
    port: 4789
    link: eno1
    mtu: 1554

[copacule (copacule)]

+1 for this

[lowid (soloradish)]

+1, and need vxlan over unicast bridge support too.

[sascha arthur (sarthur)]

+1, netplan brings me so much trouble, whatever i touched with it is either broken or not supported at all..

[Grzegorz Sikorski (gregors)]

+1

[Glenn Tanner (glenntanner3)]

Opened 2018-04-17
Deferred 2019-10-04
Any time line? 2020-10-19

[Junien F (axino)]

I would use this as well

[masterpe (michiel-y)]

Would be great if this get implemented

[David Hubbard (dhmiva)]

Not having this also means you rip out all the related bridge config from netplan as well, since you can't define a bridge using vxlan interfaces when they don't yet exist.

[Jeremy (nzlamb)]

Concur with VXLAN support. Netplan is bliss compared to wrangling systemd-networkd directly so it's a pity that Netplan only supports such a tiny subset of networkd's available capabilities.

[Michael OReilly (oreillymj)]

+1 for vxlan support

[Anthony (atimmins)]

I've submitted a PR to address this: https://github.com/canonical/netplan/pull/272

[sascha arthur (sarthur)]

pretty awesome! maybe you should squash your 116 commits.. :D

[Anthony (atimmins)]

Thanks! And yep, they've now been squashed :)

[Lukas Märdian (slyon)]

Support for VXLAN landed in netplan v0.105: https://github.com/canonical/netplan/pull/288