Skip to content

Commit 1ffee22

Browse files
jc-clarkgithub-actionsheiskrSiaraMist
authored
Add documentation for Actions: Private networking with Azure VNET (github#39075)
Co-authored-by: github-actions <[email protected]> Co-authored-by: Kevin Heis <[email protected]> Co-authored-by: Siara <[email protected]>
1 parent 70a0476 commit 1ffee22

10 files changed

+312
-8
lines changed
73.7 KB
Loading

content/actions/using-github-hosted-runners/connecting-to-a-private-network.md

Lines changed: 290 additions & 4 deletions
Large diffs are not rendered by default.

content/actions/using-github-hosted-runners/controlling-access-to-larger-runners.md

Lines changed: 11 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ versions:
77
feature: actions-hosted-runners
88
type: tutorial
99
---
10-
10+
1111
{% data reusables.actions.enterprise-github-hosted-runners %}
1212

1313
## About runner groups
@@ -79,6 +79,16 @@ For runner groups in an organization, you can change what repositories in the or
7979
- [Changing which workflows can access an organization runner group](#changing-which-workflows-can-access-an-organization-runner-group)
8080
- [Changing which workflows can access an enterprise runner group](#changing-which-workflows-can-access-an-enterprise-runner-group)
8181

82+
{% ifversion actions-private-networking-azure-vnet %}
83+
84+
## Configuring private network access for larger runners
85+
86+
{% data reusables.actions.azure-vnet-injected-runners-intro %}
87+
88+
If you have configured your enterprise to connect to an Azure VNET, you can give runner groups access to the virtual network. For more information, see "[AUTOTITLE](/actions/using-github-hosted-runners/connecting-to-a-private-network#using-an-azure-virtual-network-vnet)."
89+
90+
{% endif %}
91+
8292
### Changing which workflows can access an organization runner group
8393

8494
{% data reusables.actions.runner-groups-org-navigation %}

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

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -19,7 +19,7 @@ Enterprise owners can add {% data variables.actions.hosted_runner %}s to an ente
1919
{% data reusables.enterprise-accounts.actions-tab %}
2020
{% data reusables.enterprise-accounts.actions-runners-tab %}
2121
{% data reusables.actions.add-hosted-runner %}
22-
1. To allow organizations to access your {% data variables.actions.hosted_runner %}s, specify the list of organizations that can use it. For more information, see "[Managing access to your runners](#managing-access-to-your-runners)."
22+
{% data reusables.actions.org-access-to-github-hosted-runners %}
2323

2424
{% endif %}
2525

@@ -37,7 +37,7 @@ You can add a {% data variables.actions.hosted_runner %} to an organization, whe
3737

3838
## Allowing repositories to access {% data variables.actions.hosted_runner %}s
3939

40-
Repositories are granted access to {% data variables.actions.hosted_runner %}s through runner groups. Enterprise administrators can choose which organizations are granted access to enterprise-level runner groups, and organization administrators control repository-level access to all {% data variables.actions.hosted_runner %}s. Organization administrators can use and configure enterprise-level runner groups for the repositories in their organization, or they can create organization-level runner groups to control access.
40+
Repositories are granted access to {% data variables.actions.hosted_runner %}s through runner groups. Enterprise administrators can choose which organizations are granted access to enterprise-level runner groups, and organization administrators control repository-level access to all {% data variables.actions.hosted_runner %}s. Organization administrators can use and configure enterprise-level runner groups for the repositories in their organization, or they can create organization-level runner groups to control access.
4141

4242
- **For enterprise-level runner groups**: {% data reusables.actions.about-enterprise-level-runner-groups %}
4343
- **For organization-level runner groups**: {% data reusables.actions.about-organization-level-runner-groups %}
Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,4 @@
1+
# Reference: #9954
2+
# Documentation for larger-hosted runners with Azure Vnet injection public beta
3+
versions:
4+
ghec: '*'
Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1 @@
1+
If you are using Azure and {% data variables.product.prodname_ghe_cloud %}, you can create {% data variables.product.company_short %}-hosted runners in your Azure Virtual Network(s) (VNET). This enables you to take advantage of {% data variables.product.company_short %}-managed infrastructure for your CI/CD while providing you with full control over the networking policies of your runners. For more information about Azure VNET, see [What is Azure Virtual Network?](https://learn.microsoft.com/en-us/azure/virtual-network/virtual-networks-overview) in the Azure documentation.

data/reusables/actions/creating-a-runner-group-for-an-enterprise.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -14,6 +14,6 @@ If no group is specified during the registration process, runners are automatica
1414
When creating a group, you must choose a policy that defines which organizations have access to the runner group.
1515

1616
{% data reusables.actions.runner-groups-add-to-enterprise-first-steps %}
17-
1. To choose a policy for organization access, select the **Organization access** dropdown menu and click a policy. You can configure a runner group to be accessible to a specific list of organizations, or all organizations in the enterprise.{% ifversion ghes %} By default, only private repositories can access runners in a runner group, but you can override this.{% endif %}
17+
{% data reusables.actions.workflows.runner-groups-enterprise-organization-access %}
1818
{% data reusables.actions.runner-group-assign-policy-workflow %}
1919
1. Click **Save group** to create the group and apply the policy.
Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1 @@
1+
Using {% data variables.product.company_short %}-hosted larger runners with an Azure Virtual Network (VNET) is in beta and subject to change.
Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1 @@
1+
1. To allow organizations to access your {% data variables.actions.hosted_runner %}s, specify the list of organizations that can use it. For more information, see "[Managing access to your runners](#managing-access-to-your-runners)."
Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1 @@
1+
1. To choose a policy for organization access, select the **Organization access** dropdown menu and click a policy. You can configure a runner group to be accessible to a specific list of organizations, or all organizations in the enterprise.{% ifversion ghes %} By default, only private repositories can access runners in a runner group, but you can override this.{% endif %}

0 commit comments

Comments
 (0)