-
Notifications
You must be signed in to change notification settings - Fork 3
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
V0.43.0 hmhco #1
Conversation
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.
LGTM
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.
Few small comments - main thing is probably the pveasey to hmh
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.
LGTM
Per BEDROCK-6218
See:
https://discuss.hashicorp.com/t/delay-sigterm-of-envoy-sidecar-proxy/22036/3
hashicorp#536
for more detailed explanation of the issue
upgrades to consul k8s will break gracefulness of ingress, this PR adds a default delay of 3 seconds for the envoy sidecar. This allows enough time for consul service to be deregistered before envoy gets a SIGTERM
i have opened a ticket with hashicorp and linked this code along with details why.
They confirmed this solution is feasible approach atm.
Changes proposed in this PR:
How I've tested this PR:
How I expect reviewers to test this PR:
Checklist: