use spec.ports.name in the service manifest to uniqely generate service key used
internally to lookup services info and endpoints info maps

closes #3

Check was being made if file '/var/lib/kube-router/kubeconfig' exists even when one of the above flag was provided

explore integration of an ingress controller so Kube-router will be one complete solution for both east-west and north-south traffic

BUG 1: If service manifest has "SessionAffinity" set, then configure IPVS to provide session persistence

configure ipvs service configuration to provide persistence

on  "kube-router --cleanup-config"

by masqurading the traffic so the return traffic from the pod hits the node before
going to the client