Fixes #20

On add/remove node events, perform refresh of peers to the peers as per the
current set of active nodes. If a node is removed, delete the BGP nieghbor relation.

Fixes #14

Docs: fix curl commands in bootkube.md

by host name or FQDN. kubelet can be started with --hostname-override with configurable value.
In AWS envirinment typcally its set FQDN obtained from the metda data. This fix ensures
we can deploy kube-router in case nodes are registered with FQDN

Fixes #17

Bootkube Integration

external routers

Once external BGP is peered with cluster nodes, pods can be routable externally

fixes #4 and #7

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