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
> Install the appliance on the first machine (seed node) to ensure Azure Local deploys correctly. The setup takes a few hours and must finish successfully before you move on. Once it’s complete, you have a local control plane running in your datacenter.
364
-
365
-
If the installation fails because of incorrect network, identity, or observability settings, update the configuration object and run the `Install-appliance` command again.
366
-
367
-
You can also specify the -clean switch to start installation from scratch. This switch resets any existing installation state and starts from the beginning
366
+
>
367
+
> If the installation fails because of incorrect network, identity, or observability settings, update the configuration object and run the `Install-appliance` command again.
368
+
>
369
+
> You can also specify the -clean switch to start installation from scratch. This switch resets any existing installation state and starts from the beginning
370
+
>
371
+
> DisableChecksum = $true will skip validating the signature of the Appliance. Use this when deploying an air-gapped environment in this release. If checksum validation is enabled - the node needs to be able to reach and validate the Microsoft cert signing certificates used for signing this build.
368
372
369
373
1. Modify the configuration object.
370
374
@@ -656,7 +660,9 @@ To use the management endpoint for troubleshooting and reconfiguration, you need
656
660
From a client with network access to the management endpoint, import the **OperationsModule** and set the context (modify the script to match your configuration):
Copy file name to clipboardExpand all lines: azure-local/manage/disconnected-operations-known-issues.md
+5Lines changed: 5 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -20,6 +20,11 @@ These release notes update continuously, and we add critical issues that need a
20
20
21
21
## Known issues in the preview release
22
22
23
+
### Air-gapped deployment when local DNS forwards and resolves external domain requests
24
+
There is a known issue if you try to deploy an air-gapped enviroment - in the rare condition you would have a local DNS server that is able to resolve public (Microsoft.com) endpoints.
25
+
26
+
Mitigation: Disable DNS forwarding for microsoft.com and azure.com zones. The appliance should not be able to resolve these DNS endpoint and will fail if it receives an IP address.
27
+
23
28
### Azure Local deployment with Azure Keyvault
24
29
25
30
Role-Based Access Control (RBAC) permissions on a newly created Azure Key Vault can take up to 20 minutes to propagate. If you create the Azure Key Vault in the local portal and try to finish the cloud deployment, you might run into permission issues when validating the cluster before deployment.
0 commit comments