Skip to content

Commit 8c05eb0

Browse files
authored
DOC-1716 Azure BYOC cluster creation is missing registering 1 provider (#426)
* DOC-1716 Azure BYOC cluster creation is missing registering 1 provider * apply coderabbit suggestion
1 parent 5d5deed commit 8c05eb0

File tree

1 file changed

+25
-8
lines changed

1 file changed

+25
-8
lines changed

modules/get-started/pages/cluster-types/byoc/azure/create-byoc-cluster-azure.adoc

Lines changed: 25 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -35,34 +35,51 @@ In the https://login.microsoftonline.com/[Azure Portal^], confirm that the dedic
3535

3636
* **Role**: The Azure user must have the _Owner_ role in the subscription.
3737

38-
* **Resources**: The subscription must be registered for the following resource providers. See the https://learn.microsoft.com/en-us/azure/azure-resource-manager/management/resource-providers-and-types[Microsoft documentation^].
38+
* **Resources**: The subscription must be registered for the following resource providers (AKS + common dependencies). See the https://learn.microsoft.com/en-us/azure/azure-resource-manager/management/resource-providers-and-types[Microsoft documentation^].
3939
+
4040
--
4141
** Microsoft.Compute
4242
** Microsoft.ManagedIdentity
4343
** Microsoft.Storage
4444
** Microsoft.KeyVault
4545
** Microsoft.Network
46+
** Microsoft.ContainerService
4647
--
4748
+
48-
To check if a resource provider is registered, run the following command using the Azure CLI or in the Azure Cloud Shell. For example, to check for Microsoft.Compute, run:
49+
To check if a resource provider is registered, run the following command using the Azure CLI or in the Azure Cloud Shell:
4950
+
50-
```
51-
az provider show -n Microsoft.Compute
5251
```
53-
+
54-
If it is not registered, run:
52+
az provider show -n Microsoft.Compute --query registrationState -o tsv
53+
az provider show -n Microsoft.ManagedIdentity --query registrationState -o tsv
54+
az provider show -n Microsoft.Storage --query registrationState -o tsv
55+
az provider show -n Microsoft.KeyVault --query registrationState -o tsv
56+
az provider show -n Microsoft.Network --query registrationState -o tsv
57+
az provider show -n Microsoft.ContainerService --query registrationState -o tsv
58+
```
59+
+
60+
If a resource provider is not registered, run:
5561
+
5662
```
57-
az provider register --namespace 'Microsoft.Compute'
63+
az provider register --namespace Microsoft.Compute
64+
az provider register --namespace Microsoft.ManagedIdentity
65+
az provider register --namespace Microsoft.Storage
66+
az provider register --namespace Microsoft.KeyVault
67+
az provider register --namespace Microsoft.Network
68+
az provider register --namespace Microsoft.ContainerService
5869
```
5970

6071
* **Feature**: The subscription must be registered for Microsoft.Compute/EncryptionAtHost. See the https://learn.microsoft.com/en-us/azure/virtual-machines/linux/disks-enable-host-based-encryption-cli#prerequisites[Microsoft documentation^].
6172
+
6273
To register it, run:
6374
+
6475
```
65-
az feature register --namespace Microsoft.Compute --name EncryptionAtHost
76+
az feature register --namespace Microsoft.Compute --name EncryptionAtHost
77+
78+
# (optional) Wait and verify it shows as Registered
79+
az feature show --namespace Microsoft.Compute --name EncryptionAtHost --query properties.state -o tsv
80+
81+
# Refresh the provider after enabling a feature
82+
az provider register --namespace Microsoft.Compute
6683
```
6784

6885
* **Monitoring**: The subscription must have Azure Network Watcher enabled in the NetworkWatcherRG resource group and the region where you will use Redpanda. Network Watcher lets you monitor and diagnose conditions at a network level. See the https://learn.microsoft.com/en-us/azure/network-watcher/network-watcher-create?tabs=portaly[Microsoft documentation^].

0 commit comments

Comments
 (0)