Explicitly setting VRFs on main API and metrics API listener socket

1

I have a use case, where I would like for metrics listener to listen in a separate VRF than main Incus API, e.g. Incus API to listen on IP1 in default VRF and metrics API to listen on IP2 in separate VRF (e.g. metrics and default VRFs, both created and configured via netplan).

I can’t run incusd daemon in metrics VRF (set e.g. via systemd service definition), as that also puts main API in that VRF.

Ideally, where would be a separate config that injected socket options for both API listener socket, e.g.

incus config set core.https_address 192.168.1.1:8443
incus config set core.https.vrf default
incus config set core.metrics_address 10.0.0.1:8444
incus config set core.metrics.vrf monitoring

Thoughts?

2

I don’t know that there is any support in Go for having the process run different socket listeners in different VRFs. You’d usually do that kind of thing at the process level rather than per listener.

One workaround you could use I guess is have Incus run all its listeners in one VRF and then setup proxies on the host to your other VRFs.