[BUG] Flyte Admin Should Terminate Gracefully

[Sovietaced]

Describe the bug

Flyte Admin does not appear to respond to SIGTERM and as such does not gracefully terminate when Kubernetes is doing a rolling restart or upgrade. Servers should terminate gracefully so that they can drain buffers, connections, RPCs, etc and minimize errors or loss of data.

Expected behavior

When receiving a SIGTERM, I expect Flyte Admin to run a shutdown sequence where the RPC servers are shut down and any buffers are drained.

Additional context to reproduce

No response

Screenshots

No response

Are you sure this issue hasn't been raised already?

• Yes

Have you read the Code of Conduct?

• Yes

[lowc1012]

#take