# 0-downtime collab deploys? \(\#8926\) · gitcafe/zed

[View on GitCafe](https://git.cafe/gitcafe/zed/commit/6d538468248827608472c6ce3498b083104c55f7)

Repository: [gitcafe/zed](https://git.cafe/gitcafe/zed)

Visibility: public

Requested revision: 6d538468248827608472c6ce3498b083104c55f7

Requested commit: 6d538468248827608472c6ce3498b083104c55f7

Commit: 6d538468248827608472c6ce3498b083104c55f7

Tree: 9a3dfc9d1854a7b1df48c4a3b2e8fa34051c1794

Author: Conrad Irwin

Committer: GitHub

## Message

```
0-downtime collab deploys? (#8926)

Before this change Kubernetes would send a SIGTERM to the old server
before the new one was ready. Now it will wait.

From my reading it seems like startupProbe should not be necessary if we
have a
readinessProbe; but from testing it seems like without startupProbe we
still
drop requests when using `rollout restart`

Release Notes:

- Fixed connectivity issues during Zed deploys.
```

## Parents

- [01e5e4224a3630e5bbd38462f63bc5487048fbd6](https://git.cafe/gitcafe/zed/commit/01e5e4224a3630e5bbd38462f63bc5487048fbd6?format=markdown)

[Source at this commit](https://git.cafe/gitcafe/zed/tree/6d538468248827608472c6ce3498b083104c55f7?format=markdown)