Prevent runaway error logging on Envoy

Fixes a bug where a duplicate service port for a different service can cause Envoy to go into a tight logging loop

v2.1.5

Support websockets

v2.1.4

Minor cleanup, remove deprecation warning

v2.1.3

Support EDS from the ADS endpoints

v2.1.2

Fix handling of service names in GRPC API

Add service DRAINING status

This release adds a new DRAINING status for services as well as a handler for the drain HTTP API endpoint. This status is meant to signal that a service is going to be killed soon, so it should be taken out of service ASAP. For more details see #47.

Use IP addresses in HAproxy

This release moves to using IP addresses whenever possible in HAproxy. Sidecar also now carries IP address information in the gossip messages. If the IP address is specified on a port in Docker, it will be carried in the gossip message and used in HAproxy. If the port is bound on 0.0.0.0, then the public address of the host is used in the gossip messages and HAproxy. A configuration option of use_hostnames has been added to the sidecar.toml to revert to the previous behavior, or for scenarios where that behavior is just more desirable (e.g. NAT situations).

Don't leak goroutines from watchHandler

Fixes a bug where we could still leak a goroutine from the /watch endpoint.

Fix /watch endpoint

There was a goroutine leak in the /watch endpoint that was discovered by @bparli and was fixed in #26 and #27.

The new implementation both fixes that bug, and moves /watch to use the state listener mechanism already used by HAProxy and UrlListener

Remote Listeners

• Adds support for posting state to remote URLs
• HAproxy uses the same listener mechanism as everything else
• Minor bugfixes