You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: modules/installation-azure-identities.adoc
+4-2Lines changed: 4 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -4,10 +4,12 @@
4
4
5
5
:_mod-docs-content-type: CONCEPT
6
6
[id="installation-azure-identities_{context}"]
7
-
= Supported identities to access Azure resources
7
+
= Supported identities to access {azure-short} resources
8
8
9
-
An {product-title} cluster requires an Azure identity to create and manage Azure resources. As such, you need one of the following types of identities to complete the installation:
9
+
An {product-title} cluster requires an {azure-short} identity to create and manage {azure-short} resources. You need one of the following types of identities to complete the installation:
10
10
11
11
* A service principal
12
12
* A system-assigned managed identity
13
13
* A user-assigned managed identity
14
+
15
+
For more information on Azure identities, see link:https://learn.microsoft.com/en-us/entra/identity/managed-identities-azure-resources/overview#managed-identity-types[Managed identity types].
Copy file name to clipboardExpand all lines: modules/installation-azure-limits.adoc
+2Lines changed: 2 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -206,6 +206,8 @@ Using spot VMs for control plane nodes is not recommended.
206
206
endif::ash[]
207
207
|===
208
208
209
+
To increase an account limit, file a support request on the Azure portal. For more information, see link:https://learn.microsoft.com/en-us/azure/deployment-environments/how-to-request-quota-increase[Request a quota limit increase for Azure Deployment Environments resources].
Copy file name to clipboardExpand all lines: modules/installation-azure-marketplace.adoc
+4-4Lines changed: 4 additions & 4 deletions
Original file line number
Diff line number
Diff line change
@@ -4,13 +4,13 @@
4
4
5
5
:_mod-docs-content-type: CONCEPT
6
6
[id="installation-azure-marketplace_{context}"]
7
-
= Supported Azure Marketplace regions
7
+
= Supported {azure-short} Marketplace regions
8
8
9
-
Installing a cluster using the Azure Marketplace image is available to customers who purchase the offer in North America and EMEA.
9
+
Installing a cluster using the {azure-short} Marketplace image is available to customers who purchase the offer in North America and EMEA.
10
10
11
-
While the offer must be purchased in North America or EMEA, you can deploy the cluster to any of the Azure public partitions that {product-title} supports.
11
+
While the offer must be purchased in North America or EMEA, you can deploy the cluster to any of the {azure-short} public partitions that {product-title} supports.
12
12
13
13
[NOTE]
14
14
====
15
-
Deploying a cluster using the Azure Marketplace image is not supported for the Azure Government regions.
15
+
Deploying a cluster using the {azure-short} Marketplace image is not supported for the {azure-short} Government regions.
To install {product-title}, the Microsoft Azure account you use must
11
+
To install {product-title}, the {azure-first} account you use must
12
12
have a dedicated public hosted DNS zone in your account. This zone must be
13
13
authoritative for the domain. This service provides
14
14
cluster DNS resolution and name lookup for external connections to the cluster.
15
15
16
16
.Procedure
17
17
18
18
. Identify your domain, or subdomain, and registrar. You can transfer an
19
-
existing domain and registrar or obtain a new one through Azure or another source.
20
-
+
21
-
[NOTE]
22
-
====
23
-
For more information about purchasing domains through Azure, see
24
-
link:https://docs.microsoft.com/en-us/azure/app-service/manage-custom-dns-buy-domain[Buy a custom domain name for Azure App Service]
25
-
in the Azure documentation.
26
-
====
27
-
28
-
. If you are using an existing domain and registrar, migrate its DNS to Azure. See
19
+
existing domain and registrar or obtain a new one through {azure-short} or another source.
20
+
21
+
** To purchase a new domain through {azure-short}, see link:https://docs.microsoft.com/en-us/azure/app-service/manage-custom-dns-buy-domain[Buy a custom domain name for Azure App Service].
22
+
23
+
** If you are using an existing domain and registrar, migrate its DNS to {azure-short}. For more information, see
29
24
link:https://docs.microsoft.com/en-us/azure/app-service/manage-custom-dns-migrate-domain[Migrate an active DNS name to Azure App Service]
30
-
in the Azure documentation.
25
+
in the {azure-short} documentation.
31
26
32
-
. Configure DNS for your domain. Follow the steps in the
33
-
link:https://docs.microsoft.com/en-us/azure/dns/dns-delegate-domain-azure-dns[Tutorial: Host your domain in Azure DNS]
34
-
in the Azure documentation to create a public hosted zone for your domain or
35
-
subdomain, extract the new authoritative name servers, and update the registrar
36
-
records for the name servers that your domain uses.
27
+
. Configure DNS for your domain, which includes creating a public hosted zone for your domain or subdomain, extracting the new authoritative name servers, and updating the registrar records for the name servers that your domain uses. For more information, see
28
+
link:https://docs.microsoft.com/en-us/azure/dns/dns-delegate-domain-azure-dns[Tutorial: Host your domain in Azure DNS].
37
29
+
38
30
Use an appropriate root domain, such as `openshiftcorp.com`, or subdomain,
39
31
such as `clusters.openshiftcorp.com`.
40
32
41
-
. If you use a subdomain, follow your company's procedures to add its delegation
33
+
. If you use a subdomain, follow your organization's procedures to add its delegation
An {product-title} cluster requires an Azure identity to create and manage Azure resources. Before you create the identity, verify that your environment meets the following requirements:
11
+
Before you create the identity, verify that your environment meets the following requirements based on the identity:
11
12
12
13
* The Azure account that you use to create the identity is assigned the `User Access Administrator` and `Contributor` roles. These roles are required when:
14
+
13
15
** Creating a service principal or user-assigned managed identity.
16
+
14
17
** Enabling a system-assigned managed identity on a virtual machine.
18
+
15
19
* If you are going to use a service principal to complete the installation, verify that the Azure account that you use to create the identity is assigned the `microsoft.directory/servicePrincipals/createAsOwner` permission in Microsoft Entra ID.
16
20
17
-
To set roles on the Azure portal, see the link:https://docs.microsoft.com/en-us/azure/role-based-access-control/role-assignments-portal[Manage access to Azure resources using RBAC and the Azure portal] in the Azure documentation.
21
+
To set roles on the {azure-short} portal, see link:https://docs.microsoft.com/en-us/azure/role-based-access-control/role-assignments-portal[Assign {azure-short} roles using the {azure-short} portal] in the {azure-short} documentation.
Copy file name to clipboardExpand all lines: modules/installation-azure-preparing-diskencryptionsets.adoc
+17-17Lines changed: 17 additions & 17 deletions
Original file line number
Diff line number
Diff line change
@@ -4,42 +4,42 @@
4
4
5
5
:_mod-docs-content-type: PROCEDURE
6
6
[id="preparing-disk-encryption-sets_{context}"]
7
-
= Preparing an Azure Disk Encryption Set
8
-
The {product-title} installer can use an existing Disk Encryption Set with a user-managed key. To enable this feature, you can create a Disk Encryption Set in Azure and provide the key to the installer.
7
+
= Preparing an {azure-short} Disk Encryption Set
8
+
The {product-title} installer can use an existing Disk Encryption Set with a user-managed key. To enable this feature, you can create a Disk Encryption Set in {azure-short} and provide the key to the installer.
9
9
10
10
.Procedure
11
11
12
-
. Set the following environment variables for the Azure resource group by running the following command:
12
+
. Set the environment variables for the {azure-short} resource group by running the following command:
13
13
+
14
14
[source,terminal]
15
15
----
16
16
$ export RESOURCEGROUP="<resource_group>" \// <1>
17
17
LOCATION="<location>" <2>
18
18
----
19
-
<1> Specifies the name of the Azure resource group where you will create the Disk Encryption Set and encryption key. To avoid losing access to your keys after destroying the cluster, you should create the Disk Encryption Set in a different resource group than the resource group where you install the cluster.
20
-
<2> Specifies the Azure location where you will create the resource group.
19
+
<1> Specifies the name of the {azure-short} resource group where the Disk Encryption Set and encryption key are to be created. To prevent losing access to your keys when you destroy the cluster, create the Disk Encryption Set in a separate resource group from the one where you install the cluster.
20
+
<2> Specifies the {azure-short} location where the resource group is to be created.
21
21
+
22
-
. Set the following environment variables for the Azure Key Vault and Disk Encryption Set by running the following command:
22
+
. Set the environment variables for the {azure-short} Key Vault and Disk Encryption Set by running the following command:
$ az role assignment create --assignee $CLUSTER_SP_ID --role "<reader_role>" \// <1>
130
130
--scope $DES_RESOURCE_ID -o jsonc
131
131
----
132
-
<1> Specifies an Azure role with read permissions to the disk encryption set. You can use the `Owner` role or a custom role with the necessary permissions.
132
+
<1> Specifies an {azure-short} role with read permissions to the disk encryption set. You can use the `Owner` role or a custom role with the necessary permissions.
0 commit comments