Skip to content
This repository has been archived by the owner on Feb 27, 2023. It is now read-only.

Envoy graceful shutdown #144

Closed
stevesloka opened this issue Jun 6, 2018 · 5 comments · Fixed by #264
Closed

Envoy graceful shutdown #144

stevesloka opened this issue Jun 6, 2018 · 5 comments · Fixed by #264
Assignees
Labels
kind/feature Categorizes issue or PR as related to a new feature.

Comments

@stevesloka
Copy link
Member

stevesloka commented Jun 6, 2018

Feature Request

When restarting Envoy (i.e. upgrading, draining nodes, etc), the pod receives a SIGTERM from Kubernetes and all connections are dropped. We should signal to Envoy that it's going down and attempt to drain before rolling the pod: envoyproxy/envoy#1990 (comment)

We should be able to use the lifecycle hooks and add something like this, however, curl isn't in the envoy pod. So either we will need to add that which has our users utilize a custom image (not favorable), or we add another side-car which listens for the SIGTERM and sends the POST request to Envoy to shut down.

lifecycle:
  preStop:
  exec:
    command: ["curl","-XPOST","http://localhost:9001/healthcheck/fail"] 

// #135

@stevesloka stevesloka added the kind/feature Categorizes issue or PR as related to a new feature. label Jun 6, 2018
@rosskukulinski
Copy link
Contributor

rosskukulinski commented Jun 6, 2018

-1 to custom envoy image. But +1 on this feature.

@phylake
Copy link

phylake commented Mar 19, 2019

No curl but you do have wget

@stevesloka
Copy link
Member Author

We have this fixed in Contour (projectcontour/contour#781). I'll leave this open so that we can update the examples in Gimbal to reflect.

@azuretek
Copy link

There's still an issue projectcontour/contour#781 (review)

@davecheney
Copy link
Contributor

@steveslola can you please take this one. Thank you.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
kind/feature Categorizes issue or PR as related to a new feature.
Projects
Development

Successfully merging a pull request may close this issue.

5 participants