Skip to content

Commit b8f1c81

Browse files
authored
1 parent 1e104bd commit b8f1c81

2 files changed

Lines changed: 62 additions & 1 deletion

File tree

input/index.html.in

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -22,7 +22,7 @@ title: Documentation
2222
<h2 id="installation">Installation</h2>
2323
<p>Learn about installing the Skupper CLI and the controller.</p>
2424
<ul>
25-
<li><a href="install/index.html">Installation</a></li>
25+
<li><a href="install/index.html">Installation and upgrade</a></li>
2626
</ul>
2727

2828
<h2 id="using-the-skupper-cli-on-kubernetes">Using the Skupper CLI on Kubernetes</h2>

input/install/index.md

Lines changed: 61 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -106,3 +106,64 @@ On local systems, you can install the controller using:
106106
```bash
107107
skupper system install -p [podman, docker, linux]
108108
```
109+
110+
## Upgrading sites
111+
112+
To upgrade a site, you need to upgrade the controller using the same method you used to install Skupper, for example, one of the following:
113+
114+
* Applying the latest Helm chart
115+
* Applying the latest YAML
116+
117+
To update the Skupper CLI:
118+
119+
```bash
120+
curl https://skupper.io/v2/install.sh | sh
121+
```
122+
123+
124+
### Upgrading local sites
125+
126+
There are two distinct procedures for updating your Skupper installation: updating the site configuration and manually updating the controller.
127+
128+
**Standard Site Update**
129+
130+
To update an existing site to the latest images or configuration matching your current CLI version:
131+
132+
**Procedure**
133+
134+
1. Ensure you have the latest version of the Skupper CLI installed.
135+
2. Run the reload command:
136+
```shell
137+
skupper system reload
138+
```
139+
*This command refreshes the site definition and pulls the latest images associated with the CLI version.*
140+
141+
**Updating the controller**
142+
143+
Currently, `skupper system uninstall` protects active sites by refusing to run if a site is detected. However, if you need to force an update to the **controller** itself (to pick up a new controller version) without deleting your sites, follow this manual workaround:
144+
145+
**Prerequisites**
146+
147+
* Ensure your CLI is updated to the target version.
148+
149+
**Procedure**
150+
151+
1. Stop and remove the controller container. The container is named `<user>-skupper-controller`.
152+
153+
**Podman**
154+
```
155+
podman rm -f <user>-skupper-controller
156+
```
157+
**Docker**
158+
```
159+
docker rm -f <user>-skupper-controller
160+
```
161+
*Note: Replace `<user>` with the specific username under which Skupper is running.*
162+
163+
2. Re-install the controller.
164+
Run the install command to recreate the controller using the new CLI version.
165+
```
166+
skupper system install
167+
```
168+
169+
3. Verify the controller is recreated with the updated version.

0 commit comments

Comments
 (0)