-
Notifications
You must be signed in to change notification settings - Fork 585
use correct order of operations in termination_drain_duration description #2047
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
use correct order of operations in termination_drain_duration description #2047
Conversation
|
Hi @alam0rt. Thanks for your PR. I'm waiting for a istio member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
|
Thanks for the comprehensive debugging! /ok-to-test |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Draining does not mean rejecting all calls. The drain is graceful; it will initially just send Connection:close header. See https://www.envoyproxy.io/docs/envoy/latest/intro/arch_overview/operations/draining
Code: https://github.com/istio/istio/blob/a1c6ca2060860e97deb1f6eb12ca6770c8026672/pkg/envoy/agent.go#L102
|
By the way, in the future, the html file are auto generated from the corresponding .proto file. You should modify that file then run |
51cb50d to
3a4511a
Compare
|
/retest |
|
Thanks for getting back to me and clarifiying @howardjohn and @craigbox. I've tweaked the wording a bit to include envoy's language. As an aside, I had trouble running thanks :) |
|
/retest |
|
@alam0rt: PR needs rebase. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
|
|
@alam0rt: The following tests failed, say
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
|
/close |
Description of problem
While we were testing the
terminationDrainDurationconfig (by way of pod annotation), we realised the observed behaviour was different than what is described in the documentation.For example we set the pod's termination grace period to 30s and also the
terminationDrainDurationto 30s. We observe that the proxy allowscurlto continue establishing connections up untilSIGKILLis sent.Here we have set the
terminationDrainDurationto15s, while keeping the pod's at30s:With a curl running every
1s, we can observe that for15swe experience connection refused. Based off of this, I think it is safe to assume that theterminationDrainDurationincreases the amount of time before envoy blocks the application from making requests.Thanks to @senior88oqz for doing most of the debugging!