Merge pull request #33544 from github/repo-sync

Repo sync

Author: docs-bot

content/actions/using-github-hosted-runners/about-larger-runners/about-larger-runners.md

@@ -42,6 +42,7 @@ Compared to standard {% data variables.product.prodname_dotcom %}-hosted runners
 |                     | Ubuntu | Windows | macOS |
 | ------------------- | ------ | ------- | ----- |
 | Static IP addresses | {% octicon "check" aria-label="Supported" %} | {% octicon "check" aria-label="Supported" %} | {% octicon "x" aria-label="Not supported" %} |
+| Azure private networking | {% octicon "check" aria-label="Supported" %} | {% octicon "check" aria-label="Supported" %} | {% octicon "x" aria-label="Not supported" %} |
 | Autoscaling         | {% octicon "check" aria-label="Supported" %} | {% octicon "check" aria-label="Supported" %} | {% octicon "x" aria-label="Not supported" %} |
 | Runner groups       | {% octicon "check" aria-label="Supported" %} | {% octicon "check" aria-label="Supported" %} | {% octicon "x" aria-label="Not supported" %} |
 

data/reusables/actions/about-larger-runners.md

@@ -2,6 +2,9 @@ Customers on {% data variables.product.prodname_team %} and {% data variables.pr
 
 * More RAM, CPU, and disk space
 * Static IP addresses
+{%- ifversion actions-private-networking-azure-vnet %}
+* Azure private networking
+{%- endif %}
 * The ability to group runners
 * Autoscaling to support concurrent workflows
 * GPU-powered and ARM-powered runners

data/reusables/actions/larger-runners-troubleshooting-linux-windows.md

@@ -5,3 +5,4 @@ If you notice the jobs that target your {% data variables.actions.hosted_runner
 * **Billing information**: You must have a valid credit card on file in order to use {% data variables.actions.hosted_runner %}s. After adding a credit card to your account, it can take up to 10 minutes to enable the use of your {% data variables.actions.hosted_runner %}s. For more information, see "[AUTOTITLE](/billing/managing-your-github-billing-settings/adding-or-editing-a-payment-method)."
 * **Spending limit**: Your {% data variables.product.prodname_actions %} spending limit must be set to a value greater than zero. For more information, see "[AUTOTITLE](/billing/managing-billing-for-github-actions/managing-your-spending-limit-for-github-actions)."
 * **Fair use policy**: {% data variables.product.company_short %} has a fair use policy that begins to throttle jobs based on several factors, such as how many jobs you are running or how many jobs are running across the entirety of {% data variables.product.prodname_actions %}.
+* **Job queue to assign time**: Job queue to assign time refers to the time between a job request and {% data variables.product.company_short %} assigning a VM to execute the job. Standard {% data variables.product.company_short %}-hosted runners utilizing prescribed YAML workflow labels (such as `ubuntu-latest`) are always in a "warm" state. With larger runners, a warm machine may not be ready to pick up a job on first request as the pools for these machines are smaller. As a result, {% data variables.product.company_short %} may need to create a new VM, which increases the queue to assign time. Once a runner is in use, VMs are readily for subsequent workflow runs, reducing the queue to assign time for future workflow runs over the next 24 hours.