Skip to content

Commit

Permalink
Add docs about airgap + upgrades
Browse files Browse the repository at this point in the history
Signed-off-by: manuelbuil <[email protected]>
  • Loading branch information
manuelbuil committed Dec 19, 2024
1 parent c687bb5 commit 4450b40
Show file tree
Hide file tree
Showing 6 changed files with 32 additions and 6 deletions.
26 changes: 26 additions & 0 deletions docs/install/airgap.md
Original file line number Diff line number Diff line change
Expand Up @@ -88,3 +88,29 @@ curl -sfL https://get.rke2.io --output install.sh
INSTALL_RKE2_ARTIFACT_PATH=/root/rke2-artifacts sh install.sh
```
3. Enable and run the service as outlined [here.](quickstart.md#2-enable-the-rke2-server-service)


## Upgrading

### Manual Upgrade Method

Upgrading an air-gap environment can be accomplished in the following manner:

1. Download the new air-gap images (tar files) from the [releases](https://github.com/rancher/rke2/releases) page for the version of RKE2 you will be upgrading to. Place the tar in the `/var/lib/rancher/rke2/agent/images/` directory on each node. Delete the old tar files.
2. Follow the steps of the [manual upgrade method](../upgrades/manual_upgrade.md#manually-upgrade-rke2-using-the-binary)


### Automated Upgrades Method

RKE2 supports [automated upgrades](../upgrades/automated_upgrade.md). To enable this in air-gapped environments, you must ensure the required images are available in your private registry.

You will need the version of rancher/rke2-upgrade that corresponds to the version of RKE2 you intend to upgrade to. Note, the image tag replaces the `+` in the RKE2 release with a `-` because Docker images do not support `+`.

You will also need the versions of system-upgrade-controller and kubectl that are specified in the system-upgrade-controller manifest YAML that you will deploy. Check for the latest release of the system-upgrade-controller [here](https://github.com/rancher/system-upgrade-controller/releases/latest) and download the system-upgrade-controller.yaml to determine the versions you need to push to your private registry. For example, in release v0.4.0 of the system-upgrade-controller, these images are specified in the manifest YAML:

```
rancher/system-upgrade-controller:v0.4.0
rancher/kubectl:v0.17.0
```

Once you have added the necessary rancher/rke2-upgrade, rancher/system-upgrade-controller, and rancher/kubectl images to your private registry, follow the [automated upgrades](../upgrades/automated_upgrade.md) guide.
2 changes: 1 addition & 1 deletion docs/known_issues.md
Original file line number Diff line number Diff line change
Expand Up @@ -128,7 +128,7 @@ For more information, refer to comments on https://github.com/rancher/rke2/issue
Kubernetes removed PodSecurityPolicy from v1.25 in favor of Pod Security Standards. You can read more about PSS in the [upstream documentation](https://kubernetes.io/docs/concepts/security/pod-security-standards/). For RKE2, there are some manual steps that must be taken if the `profile` flag has been set on the nodes.

1. On all nodes, update the `profile` value to `cis-1.23`, but do not restart or upgrade RKE2 yet.
2. Perform the upgrade as normal. If using [Automated Upgrades](./upgrade/automated_upgrade.md), ensure that the namespace where the `system-upgrade-controller` pod is running in is setup to be privileged in accordance with the [Pod Security levels](https://kubernetes.io/docs/concepts/security/pod-security-admission/#pod-security-levels):
2. Perform the upgrade as normal. If using [Automated Upgrades](./upgrades/automated_upgrade.md), ensure that the namespace where the `system-upgrade-controller` pod is running in is setup to be privileged in accordance with the [Pod Security levels](https://kubernetes.io/docs/concepts/security/pod-security-admission/#pod-security-levels):
```yaml
apiVersion: v1
kind: Namespace
Expand Down
File renamed without changes.
Original file line number Diff line number Diff line change
Expand Up @@ -65,8 +65,8 @@ Or to manually upgrade rke2:

1. Download the desired version of the rke2 binary from [releases](https://github.com/rancher/rke2/releases)
2. Copy the downloaded binary to `/usr/local/bin/rke2` for tarball installed rke2, and `/usr/bin` for rpm installed rke2
3. Stop the old rke2 binary
4. Launch the new rke2 binary
3. Stop the old rke2 process
4. Launch the new rke2 process

### Upgrade rke2 Using the RPM upgrades

Expand Down
File renamed without changes.
6 changes: 3 additions & 3 deletions sidebars.js
Original file line number Diff line number Diff line change
Expand Up @@ -21,9 +21,9 @@ module.exports = {
type: 'category',
label: 'Upgrades',
items:[
'upgrade/upgrade',
'upgrade/manual_upgrade',
'upgrade/automated_upgrade',
'upgrades/upgrade',
'upgrades/manual_upgrade',
'upgrades/automated_upgrade',
],
},
{
Expand Down

0 comments on commit 4450b40

Please sign in to comment.