-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
cmd: add CLI flags for proxy shutdown lifecycle management #100
Conversation
7762e0c
to
80656fa
Compare
@mikemorris , thanks for making the PR. I am new to the world of consul-dataplane. Out of curiosity, do we have similar proxy shutdown feature in consul core ( |
Nope, this has been a longstanding feature/fix request that we're looking to address now, added relevant issue references to original post for context. The eventual implementation of graceful shutdown functionality in consul-dataplane, which these flags are intended to configure, will be managed by Helm configuration for both regular pods and jobs and triggered by a preStop hook in consul-k8s for jobs. |
5be431b
to
1ffb8ac
Compare
…gs for proxy sidecar lifecycle management
and -shutdown-grace-periods flags
1ffb8ac
to
04e73f2
Compare
e2caa1d
to
bd4d480
Compare
8ab0448
to
c687111
Compare
)" This reverts commit 3d37b9f.
* Revert "proxy-lifecycle: catch SIGTERM and initiate graceful shutdown (#130)" This reverts commit 40c99dc. * Revert "proxy-lifecycle: add HTTP Server with endpoints for proxy lifecycle shutdown (#115)" This reverts commit 0047e65. * Revert "cmd: add CLI flags for proxy shutdown lifecycle management (#100)" This reverts commit 3d37b9f.
Refs hashicorp/consul-k8s#536, hashicorp/consul-k8s#650
Adds the following CLI flags for proxy shutdown lifecycle management, disabled by default:
-shutdown-drain-listeners
-shutdown-grace-period
Adds the following CLI flags for managing where the proxy lifecycle HTTP APIs are exposed:
-graceful-shutdown-path
-graceful-port
Notes for reviewers
pkg/consuldp/consul_dataplane_test.go
has tests exclusively for required configuration, should optional flags like those being added in this PR be tested somewhere else?envoy/proxy_test.go
looks like a reasonable places to check the actual graceful shutdown behavior once implemented (and if enabled), but too broad a scope for just checking the flags set configuration properly.Should this wait to merge until the underlying functionality for these flags is implemented?-shutdown-delay
CLI flag, do we care about the naming discrepancy? The implemented functionality may differ slightly because of how we'll be handling connection draining...