fix(ollama): use Recreate deployment strategy to avoid RWO PVC mount deadlock on rollout
All checks were successful
sync-to-forgejo / sync (push) Successful in 15s
All checks were successful
sync-to-forgejo / sync (push) Successful in 15s
This commit is contained in:
parent
d503a32de7
commit
4ea0e2ae43
1 changed files with 8 additions and 0 deletions
|
|
@ -7,6 +7,14 @@ metadata:
|
||||||
app: ollama
|
app: ollama
|
||||||
spec:
|
spec:
|
||||||
replicas: 1
|
replicas: 1
|
||||||
|
# Default RollingUpdate deadlocks here: the new pod can't mount the
|
||||||
|
# ollama-models PVC (ReadWriteOnce) until the old pod releases it, but
|
||||||
|
# the old pod isn't terminated until the new one is Ready — a rollout
|
||||||
|
# that discovered this the hard way (stuck ContainerCreating). Recreate
|
||||||
|
# accepts a brief gap in availability in exchange for actually rolling
|
||||||
|
# out.
|
||||||
|
strategy:
|
||||||
|
type: Recreate
|
||||||
selector:
|
selector:
|
||||||
matchLabels:
|
matchLabels:
|
||||||
app: ollama
|
app: ollama
|
||||||
|
|
|
||||||
Loading…
Add table
Reference in a new issue