Skip to content

Commit 8987009

Browse files
docs: Explain upgrade process (argoproj#2424)
Signed-off-by: Kostis Kapelonis <[email protected]> Signed-off-by: Kostis Kapelonis <[email protected]>
1 parent cc3b148 commit 8987009

File tree

1 file changed

+15
-0
lines changed

1 file changed

+15
-0
lines changed

docs/installation.md

Lines changed: 15 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -95,3 +95,18 @@ For example if the latest minor version of Argo Rollouts is 1.2.1 and supported
9595
* Argo Rollouts 1.2.1 on Kubernetes 1.24
9696
* Argo Rollouts 1.2.1 on Kubernetes 1.23
9797

98+
## Upgrading Argo Rollouts
99+
100+
Argo Rollouts is a Kubernetes controller that doesn't hold any external state. It is active
101+
only when deployments are actually happening.
102+
103+
To upgrade Argo Rollouts:
104+
105+
1. Try to find a time period when no deployments are happening
106+
2. Delete the previous version of the controller and apply/install the new one
107+
3. When a new Rollout takes place the new controller will be activated.
108+
109+
If deployments are happening while you upgrade the controller, then you shouldn't
110+
have any downtime. Current Rollouts will be paused and as soon as the new controller becomes
111+
active it will resume all in-flight deployments.
112+

0 commit comments

Comments
 (0)