Fix Forgejo deployment hanging in Argo CD sync
Change deployment strategy from RollingUpdate (default) to Recreate to resolve volume attachment conflict. The forgejo-data PVC uses ReadWriteOnce access mode, which only allows attachment to one pod at a time. RollingUpdate tries to start new pod before terminating old pod, causing multi-attach error. With Recreate strategy, old pod terminates first, volume detaches, then new pod starts and successfully attaches the volume. Resolves: DEV-380 Co-Authored-By: Paperclip <noreply@paperclip.ing>
This commit is contained in:
parent
8c2cc6fa27
commit
ef5ef56784
1 changed files with 2 additions and 0 deletions
|
|
@ -5,6 +5,8 @@ metadata:
|
||||||
namespace: forgejo
|
namespace: forgejo
|
||||||
spec:
|
spec:
|
||||||
replicas: 1
|
replicas: 1
|
||||||
|
strategy:
|
||||||
|
type: Recreate
|
||||||
selector:
|
selector:
|
||||||
matchLabels:
|
matchLabels:
|
||||||
app: forgejo
|
app: forgejo
|
||||||
|
|
|
||||||
Loading…
Add table
Reference in a new issue