From 083fdf7371174544a5b27741b3b59c6777a08fa8 Mon Sep 17 00:00:00 2001 From: Vanessa Date: Fri, 17 May 2024 08:00:54 +1000 Subject: [PATCH] Pre-flight checks for GHES upgrades [GA] (#50545) --- .../upgrade-requirements.md | 2 ++ .../upgrading-github-enterprise-server.md | 2 ++ data/reusables/enterprise_installation/preflight-checks.md | 1 + 3 files changed, 5 insertions(+) create mode 100644 data/reusables/enterprise_installation/preflight-checks.md diff --git a/content/admin/monitoring-managing-and-updating-your-instance/updating-the-virtual-machine-and-physical-resources/upgrade-requirements.md b/content/admin/monitoring-managing-and-updating-your-instance/updating-the-virtual-machine-and-physical-resources/upgrade-requirements.md index 76ce7c5e07..aaeb484930 100644 --- a/content/admin/monitoring-managing-and-updating-your-instance/updating-the-virtual-machine-and-physical-resources/upgrade-requirements.md +++ b/content/admin/monitoring-managing-and-updating-your-instance/updating-the-virtual-machine-and-physical-resources/upgrade-requirements.md @@ -50,6 +50,8 @@ curl -s http://localhost:9201/audit_log/_stats/store | jq ._all.primaries.store. Use the number to estimate the amount of disk space the MySQL audit logs will need. The script also monitors your free disk space while the import is in progress. Monitoring this number is especially useful if your free disk space is close to the amount of disk space necessary for migration. +{% data reusables.enterprise_installation.preflight-checks %} + {% ifversion mysql-8-upgrade %} ## Known issues diff --git a/content/admin/monitoring-managing-and-updating-your-instance/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server.md b/content/admin/monitoring-managing-and-updating-your-instance/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server.md index 960844a31c..60df790446 100644 --- a/content/admin/monitoring-managing-and-updating-your-instance/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server.md +++ b/content/admin/monitoring-managing-and-updating-your-instance/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server.md @@ -37,6 +37,8 @@ To upgrade an instance, you must plan and communicate the upgrade, choose the ap To successfully upgrade {% data variables.location.product_location %}, the instance's data disk must be at least 15% free. {% data variables.product.company_short %} recommends ensuring there is more free storage on the disk. In some rare cases, for customers with large data volumes, this threshold may differ. +{% data reusables.enterprise_installation.preflight-checks %} + ## Preparing to upgrade To prepare for an upgrade, plan the upgrade path, optionally upgrade {% data variables.product.prodname_actions %} runners, and schedule a maintenance window. diff --git a/data/reusables/enterprise_installation/preflight-checks.md b/data/reusables/enterprise_installation/preflight-checks.md new file mode 100644 index 0000000000..018a1ffcd0 --- /dev/null +++ b/data/reusables/enterprise_installation/preflight-checks.md @@ -0,0 +1 @@ +When upgrading, pre-flight checks evaluate if the minimum requirements for system hardware resources, such as memory, CPU cores, and user and root disk storage, are available to your instance. If pre-flight checks determine there are insufficient resources, or otherwise fail, you are notified and the upgrade is aborted.