Backport of proxy-lifecycle: add HTTP Server with endpoints for proxy lifecycle shutdown into release/1.0.x

[hc-github-team-consul-core]

Backport

This PR is auto-generated from #115 to be assessed for backporting due to the inclusion of the label backport/1.0.

WARNING automatic cherry-pick of commits failed. Commits will require human attention.

merge conflict error: POST https://api.github.com/repos/hashicorp/consul-dataplane/merges: 409 Merge conflict []

The below text is copied from the body of the original PR.

---

Refs hashicorp/consul-k8s#536, hashicorp/consul-k8s#650

Adds a proxy lifecycle management server and starts it from the consul-dataplane main process. This server exposes an HTTP endpoint (configurable, defaulting to /graceful_shutdown on port 20300) to optionally start draining inbound (external) connections to the managed Envoy proxy, while allowing outbound requests from the application for which this proxy is acting as a sidecar to continue, up to a configurable grace period timeout, to facilitate application shutdown.

Refactors the envoy package proxy manager to introduce new states (stateDraining and stateExited) and new methods (Drain(), Quit() and renaming Stop() to Kill() to avoid confusion and better describe the actual implementation) and implement an interface to allow a mock implementation for testing the lifecycle management server in isolation.

Notes for reviewers

• This behavior can currently only be triggered by calling the /graceful_shutdown endpoint explicitly (which will be necessary for handling job termination from a preStop hook) in the future.
  • proxy-lifecycle: catch SIGTERM and initiate graceful shutdown #130 will catch SIGTERM to handle shutdown gracefully if configured, and will include an addition to the integration test.
• The additional functionality added to the envoy package does not have proper test coverage yet - I'm hoping to add this as a followup by replacing the current fake-envoy implementation with a Go-based version to include an HTTP server mocking the /drain_listeners and /quitquitquit Envoy admin API endpoints.
• Should bootstrap tests be added for the Envoy drain time and strategy passthrough configuration?
• envoyExtraArgs refactor will likely conflict with fix: log level present in extra args using envoy-extra-args annotation : NET-2190 #133 and need to be resolved

Links

• https://www.envoyproxy.io/docs/envoy/latest/intro/arch_overview/operations/draining
• https://www.envoyproxy.io/docs/envoy/latest/operations/admin#operations-admin-interface-drain
• https://www.envoyproxy.io/docs/envoy/latest/operations/cli#cmdoption-drain-time-s
• https://www.envoyproxy.io/docs/envoy/latest/operations/cli#cmdoption-drain-strategy

---

Overview of commits

• 937d893 - 722f263 - 2af6219 - a1c21c9 - 68f206d - 892392d - bb0f87a - cde897a - 471a087 - 5b54f12 - 2852040 - bbb3785 - c7e8f86 - ae041fc - 52e5fd5 - 095aaf0 - 2b0f0ee - bf9acdb - 9833553 - f0dfd78 - 7f9b0f0 - 8c8141c - f98ce24 - 91a5b81 - bfea751 - aadfeed - 496d196 - 4340c2f - 52b4557 - 21595f0 - b5e3aea - bf8f0c8 - 790881e

[curtbushko]

Going to do this manually.