programming only Local Endpoint in KUBE-LOOP_BACK

[hanamantagoudvk]

This PR contains following code changes:

a) "local" flag present in EndPoint struct is being populated correctly based on NodeName field.
This flag is important in ipvs backend to decide whether to add or not , the endpoint details into KUBE-LOOP_BACK ipset.
Hence the changes are made in kpng controller before storing the endpoint into the tree. Same flag can be used by other backends as well to know whether the endpoint is local or remote for that node.

b) Older IPVS backend is removed as its not required anymore.

[mcluseau]

hi, there a no informations about local things in the global model. The locality information is provided when the global model is converted to the local one. See https://github.com/kubernetes-sigs/kpng/blob/master/client/localsink/localsink.go#L29 for the struct to put in the backend: it gives a func BindFlags to be used by the built command (see https://github.com/kubernetes-sigs/kpng/blob/master/cmd/kpng/storecmds/storecmds.go#L122).

Note that this is something that will be refactored to the registration mecanism we want to build for dynamic commands depending on the environment (linux/windows) and to allow easy custom binaries.

[mcluseau]

/approve
/lgtm

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: hanamantagoudvk, mcluseau

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [mcluseau]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment