Skip to content

W-19396065-infrastructure-upgrade #390

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
luanamulesoft wants to merge 2 commits into
base: latest
Choose a base branch
from
Open

W-19396065-infrastructure-upgrade #390

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
3e815e9
W-19396065-infrastructure-upgrade
luanamulesoft Mar 6, 2026
ac47340
changes
luanamulesoft Mar 6, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 3 additions & 2 deletions cloudhub-2/modules/ROOT/pages/ch2-patch-updates.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -33,7 +33,8 @@ To prevent this kind of error, use the Recreate update strategy.

Schedule infrastructure upgrades earlier than the scheduled patching process, between the Release Available and the Auto-Update dates stated in the xref:release-notes::cloudhub-2/cloudhub-2-runtimes-release-notes.adoc[monthly updates table]. This way, you can choose a date in the future that better suits your organization's needs.

On average, this upgrade takes between thirty to sixty minutes to complete. If your upgrade is queued, it can take longer than thirty minutes. The impact of the upgrade process on running applications is consistent with the auto-patching behavior described in the previous sections.
[NOTE]
For both scheduled and opt-in early infrastructure upgrades, the upgrade takes on average 30 to 60 minutes to complete. If your upgrade is queued, it can take longer than 30 minutes. In some cases, unexpected infrastructure delays, such as log processing retries, can extend the upgrade beyond this window. The impact of the upgrade process on running applications is consistent with the auto-patching behavior described in the previous sections.

You can modify or delete your scheduled upgrade if it is not already in progress, as indicated by the `Queued` status. If you cancel the schedule and do not create another or opt in to an earlier upgrade, the upgrade occurs during the mandatory patching window.

Expand All @@ -54,7 +55,7 @@ After applying the upgrade, you can check the status under the *Infra Status* co

Opt in to apply infrastructure upgrades earlier than the scheduled patching process, between the Release Available and the Auto-Update dates stated in the xref:release-notes::cloudhub-2/cloudhub-2-runtimes-release-notes.adoc[monthly updates table]. This way, you can choose the time that better suits your organization's needs.

On average, this upgrade takes between thirty to sixty minutes to complete. If your upgrade is queued, it can take longer than thirty minutes. The impact of the upgrade process on running applications is consistent with the auto-patching behavior described in the previous sections.
The upgrade duration and impact are the same as for xref:ch2-patch-updates.adoc#self-upgrade-schedule[scheduled upgrades].

[NOTE]
This upgrade is irreversible. Ensure that you understand the impact of the upgrade and choose when to trigger the upgrade based on your organization's needs before applying it in a production environment.
Expand Down