Pods can now be cordoned before a deploy
You can now cordon a pod so the proxy stops sending it new connections while existing ones drain. Rolling and blue-green deploys use this automatically; you can also do it by hand:
lark pod cordon 3d8e1f2a9c4b70
lark pod uncordon 3d8e1f2a9c4b70Cordoned pods show up with a cordoned state in lark status.
Related topics
- Show & Tell: a tiny job runner on pods that sleep between jobs2 replies
- Pod stuck in "starting" for 15 hours after resume1 reply
- New pods that mount a secret as a file are destroyed within one second2 replies
- The back porch: what are you running on a single shared-cpu pod?3 replies
- Burrows: persistent sandboxes that sleep when idle3 replies
- Node.js app memory climbs until OOM — only on Larkhost2 replies