Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
chore: use ‹k8s_apply=true› by default
• Summary Initially I wanted to do ‹k8s_apply=false› for postgres, and key-value databases (such as Redis, Redict, or Valkey), because deploying on prod with ‹k8s_apply=true› caused redeployment of the postgres which caused a small outage (~5 minutes). Right now when I tried to redeploy stage multiple times in a row, none of the deployed services got redeployed, hence I come to the conclusion that there were some changes on the production deployment that were applied back then. • Context from #360 · What it actually does? In the simple terms, it makes sure that the definition that is to be deployed matches the one that is already deployed. The difference has already manifested few times, e.g., when @majamassarini was adjusting the `/dev/shm` for the postgres deployment (bedef20), the change did not get deployed. · Why some tasks already use it (e.g., Redis/Redict, Flower secret) and others not? not sure · Would it make sense to default to ‹apply=true›? Yes, but at the same time, applying meaningless changes to critical services, e.g., postgres or Redis/Redict/Valkey, can cause smaller outages. Fixes #360 Signed-off-by: Matej Focko <[email protected]>
- Loading branch information