This commit adds changes to comment a portion of kube-router source where it disables policy based routing which it does with the aid of ip in ip tunneling, the idea is that kube-router should not remove the ip rule added by us to enable policy based routing.

This commit adds changes to disable overlay for kube-router. Motivation for this change are 2 reasons. Overlay is used to help pod to pod networking across nodes in different subnets with ip in ip tunneling. However we only have 1 node, so this is not really required.

Moving on, kube-router introduced change to automatically set MTU of kube-bridge interface in https://github.com/cloudnativelabs/kube-router/pull/989. With this change kube-router gets the MTU of the host interface which is being consumed by kubernetes and then does a -20 on the MTU value ( to account for ip in ip tunneling ) and sets the kube-bridge MTU to that value. This ends up with kube-bridge mostly using 1480 if host interface was 1500 ( which is the usual case ). Issue happens that some servers send length of 1440 with fragmentation flag unset which results in the packet getting dropped as the packet size is larger then what the interface can handle. I am discussing this with a kube-router developer and would make an issue upstream as well once he finalizes the scope.

This change fixes our TLS issues where popular sites like github could not be accessed reliably and we did not require ip in ip tunneling because that's not our use case, so from that aspect it's fine to disable overlay.

I found that without taking a brief pause between iptables cleanup and
ipset deletion, sometimes the system still thought that there were
iptables references to the ipsets and would error instead of cleaning
the ipsets.

Errors can happen here for a lot of reasons, the user may not have been
running the controller, the definitions may have already been deleted,
the ipset may not be around to be referenced because the user already
cleaned up before.

Reduced the logging to trim user confusion over error statements in the
logs.

Use existing cleanupStale*() methods to cleanup NPC based iptables and
ipsets. This provides a more consistent method of cleanup, consolidates
the logic, and updates it for all of the changes NPC has gone through.

Somehow I missed adding ipset locking around cleanupStaleIPSets()

Don't continue the loop if we've already matched.

Bumps [k8s.io/klog/v2](https://github.com/kubernetes/klog) from 2.9.0 to 2.10.0.
- [Release notes](https://github.com/kubernetes/klog/releases)
- [Changelog](https://github.com/kubernetes/klog/blob/main/RELEASE.md)
- [Commits](https://github.com/kubernetes/klog/compare/v2.9.0...v2.10.0

)

---
updated-dependencies:
- dependency-name: k8s.io/klog/v2
  dependency-type: direct:production
  update-type: version-update:semver-minor
...
Signed-off-by: dependabot[bot] <support@github.com>

Bumps [k8s.io/cri-api](https://github.com/kubernetes/cri-api) from 0.21.2 to 0.21.3.
- [Release notes](https://github.com/kubernetes/cri-api/releases)
- [Commits](https://github.com/kubernetes/cri-api/compare/v0.21.2...v0.21.3

)

---
updated-dependencies:
- dependency-name: k8s.io/cri-api
  dependency-type: direct:production
  update-type: version-update:semver-patch
...
Signed-off-by: dependabot[bot] <support@github.com>

Bumps [k8s.io/client-go](https://github.com/kubernetes/client-go) from 0.21.2 to 0.21.3.
- [Release notes](https://github.com/kubernetes/client-go/releases)
- [Changelog](https://github.com/kubernetes/client-go/blob/master/CHANGELOG.md)
- [Commits](https://github.com/kubernetes/client-go/compare/v0.21.2...v0.21.3

)

---
updated-dependencies:
- dependency-name: k8s.io/client-go
  dependency-type: direct:production
  update-type: version-update:semver-patch
...
Signed-off-by: dependabot[bot] <support@github.com>

Dependabot does not have access to secrets, so skip building containers

* remove IPVS metrics

Remove metrics for IPVS services when the IPVS service is deleted so
that the number of metrics does not grow without bound.

Fixes #734

* delete metricsMap key when IPVS service is removed

Delete the key in NetworkServicesController.metricsMap when the
respective IPVS configuration is removed.

Remove a period from a comment to conform to kube-router norms

* cleanup stale metrics in a distinct method

* remove unnecessary error return value on cleanupStaleMetrics

Avoid extra and unneeded work by processing withdrawls first. Also makes
the logic a lot more clear.

This also makes the call that happens upon path withdrawl safer, by
checking to see if the route exists before deleting it.

One departure here is that we used to only log errors, now we return
errors as soon as they are encountered, this may cause some routes to
persist even if they had been cleaned before by stopping at the first
error. However, I think that it makes for more consistent and expected
behavior if this needs to be called in another place.

* Removes Travis Integration and migrates to Github Actions
* Builds binaries in Dockerfile via MultiArch
* Adds a Release Process
* Drops support for ppc64le, s390x container builds (as golang-alpine3.14 does not
  contain builds for them)

Bumps [github.com/prometheus/client_golang](https://github.com/prometheus/client_golang) from 1.10.0 to 1.11.0.
- [Release notes](https://github.com/prometheus/client_golang/releases)
- [Changelog](https://github.com/prometheus/client_golang/blob/master/CHANGELOG.md)
- [Commits](https://github.com/prometheus/client_golang/compare/v1.10.0...v1.11.0

)

---
updated-dependencies:
- dependency-name: github.com/prometheus/client_golang
  dependency-type: direct:production
  update-type: version-update:semver-minor
...
Signed-off-by: dependabot[bot] <support@github.com>