Skip to content

S
system-charts
Commit dd0ab35d by gitlawr Committed by Alena Prokharchyk
Options

Set maxUnavailable to 1 for registry deployment

Problem: Registry pod stuck in AttchVolumeFailed status on upgrade. Deadlock happens where the new pod waits the old pod to dettach the volume, and the old one waits for the new one to be ready. Solution: Set maxUnavailable to 1, so that the old pod can be released before the new pod is ready.
parent dd6b3832
Showing with 3 additions and 0 deletions
charts/harbor/v1.7.5-rancher1/templates/registry/registry-dpl.yaml
...@@ -11,6 +11,9 @@ spec: ...@@ -11,6 +11,9 @@ spec:
matchLabels: matchLabels:
{{ include "harbor.matchLabels" . | indent 6 }} {{ include "harbor.matchLabels" . | indent 6 }}
component: registry component: registry
strategy:
rollingUpdate:
maxUnavailable: 1
template: template:
metadata: metadata:
labels: labels:
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment