Merge pull request #33006 from github/repo-sync

Repo sync

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

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.

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.