viktor/infra
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

[ci skip] Use RollingUpdate strategy for real-estate-crawler deployments

Browse source 
Set max_unavailable=0, max_surge=1 on both UI and API deployments
to ensure at least 1 replica is always available during updates.
This commit is contained in:
Viktor Barzin 2026-02-10 21:28:38 +00:00
parent 348d706a48
commit f9c07f015b
No known key found for this signature in database
GPG key ID: 0EB088298288D958
2 changed files with 12 additions and 4 deletions
Download patch file Download diff file Expand all files Collapse all files

16
modules/kubernetes/real-estate-crawler/main.tf
View file

@ -33,9 +33,13 @@ resource "kubernetes_deployment" "realestate-crawler-ui" {
} }
spec { spec {
replicas = 1 replicas = 1
# strategy { strategy {
# type = "RollingUpdate" # DB is external so we can roll type = "RollingUpdate"
# } rolling_update {
max_unavailable = 0
max_surge = 1
}
}
selector { selector {
match_labels = { match_labels = {
app = "realestate-crawler-ui" app = "realestate-crawler-ui"
@ -102,7 +106,11 @@ resource "kubernetes_deployment" "realestate-crawler-api" {
spec { spec {
replicas = 1 replicas = 1
strategy { strategy {
type = "Recreate" type = "RollingUpdate"
rolling_update {
max_unavailable = 0
max_surge = 1
}
} }
selector { selector {
match_labels = { match_labels = {

BIN
terraform.tfstate
View file

Binary file not shown.