fix(gitea): use Recreate strategy to prevent LevelDB lock conflict
SQLite and LevelDB can't be accessed by two pods simultaneously. RollingUpdate starts a new pod before the old one stops, causing the queue lock to fail on startup. Recreate terminates the old pod first. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
This commit is contained in:
parent
6dd7592ac9
commit
92fc9843c2
@ -89,6 +89,10 @@ resource "helm_release" "gitea" {
|
|||||||
storageClass = "local-path"
|
storageClass = "local-path"
|
||||||
}
|
}
|
||||||
|
|
||||||
|
strategy = {
|
||||||
|
type = "Recreate"
|
||||||
|
}
|
||||||
|
|
||||||
resources = {
|
resources = {
|
||||||
requests = { cpu = "100m", memory = "256Mi" }
|
requests = { cpu = "100m", memory = "256Mi" }
|
||||||
limits = { cpu = "500m", memory = "512Mi" }
|
limits = { cpu = "500m", memory = "512Mi" }
|
||||||
|
|||||||
Loading…
x
Reference in New Issue
Block a user