Fix ovs examples

[ljkiraly]

Remove cpu resource limit from forwarder app configuration
Re-add ovs-forwarder tests to remote vlan examples

Signed-off-by: Laszlo Kiraly laszlo.kiraly@est.tech

Using debug PRs I was able to find the reason why cmd-forwarder-ovs does not started during integration test run in GihHub. The kubectl describe pod command output revealed why the scheduling failed:

Warning  FailedScheduling  23s (x4 over 4m)  default-scheduler  0/3 nodes are available: 1 Insufficient cpu, 1 node(s) didn't match Pod's node affinity/selector, 1 node(s) had taint {node-role.kubernetes.io/master: }, that the pod didn't tolerate. TestRunRvlanSuiteSingle/Rvlanovs=stdout

The kind worker nodes can allocate 2 CPUs:

time=2022-04-13T14:14:25Z level=info msg=kubectl get nodes -o jsonpath='{range .items[*]}{.metadata.name}{": "}{.status.allocatable}{"\n"}{end}' --selector='!node-role.kubernetes.io/master' TestRunRvlanSuiteSingle/Rvlanovs=stdin
918
time=2022-04-13T14:14:25Z level=info msg=kind-worker: {"cpu":"2","ephemeral-storage":"87218124Ki","hugepages-1Gi":"0","hugepages-2Mi":"0","memory":"7113132Ki","pods":"110"}
919
kind-worker2: {"cpu":"2","ephemeral-storage":"87218124Ki","hugepages-1Gi":"0","hugepages-2Mi":"0","memory":"7113132Ki","pods":"110"} TestRunRvlanSuiteSingle/Rvlanovs=stdout

I did not find any system requirement in Open vSwitch documentation regarding the CPU so I removed this resource limit. The kind jobs ran successfully after this change:
https://github.com/networkservicemesh/integration-k8s-kind/actions/runs/2162217426