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: articles/azure-arc/resource-bridge/deploy-cli.md
+7-7Lines changed: 7 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -17,7 +17,7 @@ ms.topic: overview
17
17
18
18
This topic provides an overview of the [Azure CLI commands](/cli/azure/arcappliance) that are used to manage Arc resource bridge (preview) deployment, in the order in which they are typically used for deployment.
19
19
20
-
## az arcappliance createconfig
20
+
## `az arcappliance createconfig`
21
21
22
22
This command creates the configuration files used by Arc resource bridge. Credentials that are provided during `createconfig`, such as vCenter credentials for VMware vSphere, are stored in a configuration file and locally within Arc resource bridge. These credentials should be a separate user account used only by Arc resource bridge, with permission to view, create, delete, and manage on-premises resources. If the credentials change, then the credentials on the resource bridge should be updated.
23
23
@@ -30,27 +30,27 @@ This command also calls the `validate` command to check the configuration files.
30
30
> [!NOTE]
31
31
> Azure Stack HCI and Hybrid AKS use different commands to create the Arc resource bridge configuration files.
32
32
33
-
## az arcappliance validate
33
+
## `az arcappliance validate`
34
34
35
35
The `validate` command checks the configuration files for a valid schema, cloud and core validations (such as management machine connectivity to [required URLs](network-requirements.md)), network settings, and proxy settings. It also performs tests on identity privileges and role assignments, network configuration, load balancer configuration and content delivery network connectivity.
36
36
37
-
## az arcappliance prepare
37
+
## `az arcappliance prepare`
38
38
39
39
This command downloads the OS images from Microsoft that are used to deploy the on-premises appliance VM. Once downloaded, the images are then uploaded to the local cloud image gallery to prepare for the creation of the appliance VM.
40
40
41
41
This command takes about 10-30+ minutes to complete, depending on the network speed. Allow the command to complete before continuing with the deployment.
42
42
43
-
## az arcappliance deploy
43
+
## `az arcappliance deploy`
44
44
45
45
The `deploy` command deploys an on-premises instance of Arc resource bridge as an appliance VM, bootstrapped to be a Kubernetes management cluster. This command gets all necessary pods and agents within the Kubernetes cluster into a running state. Once the appliance VM is up, the kubeconfig file is generated.
46
46
47
-
## az arcappliance create
47
+
## `az arcappliance create`
48
48
49
49
This command creates Arc resource bridge in Azure as an ARM resource, then establishes the connection between the ARM resource and on-premises appliance VM.
50
50
51
51
Once the `create` command initiates the connection, it will return in the terminal, even though the connection between the ARM resource and on-premises appliance VM is not yet complete. The resource bridge needs about 5 minutes to establish the connection between the ARM resource and the on-premises VM.
52
52
53
-
## az arcappliance show
53
+
## `az arcappliance show`
54
54
55
55
The `show` command gets the status of the Arc resource bridge and ARM resource information. It can be used to check the progress of the connection between the ARM resource and on-premises appliance VM.
56
56
@@ -62,7 +62,7 @@ While the Arc resource bridge is connecting the ARM resource to the on-premises
62
62
63
63
Successful Arc resource bridge creation results in `ProvisioningState = Succeeded` and `Status = Running`.
64
64
65
-
## az arcappliance delete
65
+
## `az arcappliance delete`
66
66
67
67
This command deletes the appliance VM and Azure resources. It doesn't clean up the OS image, which remains in the on-premises cloud gallery.
0 commit comments