Support in VM and pods for VRF (kernel module)

[ghost]

I'm porting a virtualized network testbed from a system container. A correct migration requires moving the network pod's interface and routes into a non-default VRF. A large number of network namespaces compose the virtual net. bradmwalker/wanmap#48

VRF is enabled in Ubuntu 18.04+ and Fedora 29+.

The exact command to reproduce the issue:
minikube ssh
$ zcat /proc/config.gz | grep CONFIG_NET_VRF

$ sudo ip link add vrf-cluster type vrf
RTNETLINK answers: Operation not supported

[brad@x220 ~]$ minikube version
minikube version: v1.3.1
commit: ca60a42

Minikube VM is freshly created with kvm2 driver.

[tstromberg]

Sounds good. Do you mind sending a PR over to enable this?

Example PR: #4340
Documentation: https://minikube.sigs.k8s.io/docs/contributing/iso/

[sharifelgamal]

This is still a good idea.

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

[ghost]

/assign

[ghost]

/remove-lifecycle rotten