centersl/portainer-docs
1
0
Fork 0
mirror of https://github.com/portainer/portainer-docs.git synced 2026-03-27 04:48:31 +07:00
Code Issues Packages Projects Releases Wiki Activity

GITBOOK-65: Fix required naming for private registry Edge Agent and updater images

Browse Source
This commit is contained in:
James Carppe
2023-08-23 04:32:07 +00:00
committed by gitbook-bot
parent c3e008a887
commit c2a22964f8
1 changed files with 14 additions and 14 deletions
Download Patch File Download Diff File Expand all files Collapse all files

28
admin/environments/update.md
View File

@@ -20,13 +20,13 @@ To add a new update schedule, click the **Add update & rollback schedule** butto
To schedule an update, Portainer must have a snapshot of all the environments you wish to upgrade.
{% endhint %}
| Field/Option | Overview |
| -------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Name | Enter a name for the scheduled update. |
| Groups | Select the Edge Group(s) containing the Edge devices you want to update. You can configure these groups under [Edge Groups](../../user/edge/groups.md). |
| Version | Ensure the **Update** tab is selected, then select the version you want to upgrade to from the dropdown. |
| Schedule date & time | <p>Select a date and time to schedule the update.<br>When upgrading from a version prior to 2.17, this field will be unavailable and the upgrade will take place immediately on creation of the schedule.</p> |
| Registry | If needed, you can select the registry to pull the updated Portainer Agent images from. The image you are updating to must exist in the registry with the `portainer/agent:version` name format, as must the `portainer-updater` image. This functionality is useful if you are running in an airgapped environment. |
| Field/Option | Overview |
| -------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Name | Enter a name for the scheduled update. |
| Groups | Select the Edge Group(s) containing the Edge devices you want to update. You can configure these groups under [Edge Groups](../../user/edge/groups.md). |
| Version | Ensure the **Update** tab is selected, then select the version you want to upgrade to from the dropdown. |
| Schedule date & time | <p>Select a date and time to schedule the update.<br>When upgrading from a version prior to 2.17, this field will be unavailable and the upgrade will take place immediately on creation of the schedule.</p> |
| Registry | If needed, you can select the registry to pull the updated Portainer Agent images from. The image you are updating to must exist in the registry with the `agent:version` name format, as must the `portainer-updater` image. This functionality is useful if you are running in an airgapped environment. |
<figure><img src="../../.gitbook/assets/2.18-environments-update-updatescheduler.png" alt=""><figcaption></figcaption></figure>
@@ -42,13 +42,13 @@ To schedule the rollback of an update, click the **Add update & rollback schedul
To schedule a rollback, Portainer must have a snapshot of all the environments you wish to roll back.
{% endhint %}
| Field/Option | Overview |
| -------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Name | Enter a name for the scheduled rollback. |
| Group | Select the Edge Group(s) containing the Edge devices you want to roll back. You can configure these groups under [Edge Groups](../../user/edge/groups.md). |
| Version | <p>Ensure the <strong>Rollback</strong> tab is selected, then select the version you want to roll back to from the dropdown.<br>This dropdown is only available when multiple rollback versions are available.</p> |
| Schedule date & time | Select a date and time to schedule the rollback. |
| Registry | If needed, you can select the registry to pull the Portainer Agent images from. The image you are rolling back to must exist in the registry with the `portainer/agent:version` name format, as must the `portainer-updater` image. This functionality is useful if you are running in an airgapped environment. |
| Field/Option | Overview |
| -------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| Name | Enter a name for the scheduled rollback. |
| Group | Select the Edge Group(s) containing the Edge devices you want to roll back. You can configure these groups under [Edge Groups](../../user/edge/groups.md). |
| Version | <p>Ensure the <strong>Rollback</strong> tab is selected, then select the version you want to roll back to from the dropdown.<br>This dropdown is only available when multiple rollback versions are available.</p> |
| Schedule date & time | Select a date and time to schedule the rollback. |
| Registry | If needed, you can select the registry to pull the Portainer Agent images from. The image you are rolling back to must exist in the registry with the `agent:version` name format, as must the `portainer-updater` image. This functionality is useful if you are running in an airgapped environment. |
<figure><img src="../../.gitbook/assets/2.17-environments-update-rollback.png" alt=""><figcaption></figcaption></figure>