Skip to content

Commit e5f3931

Browse files
committed
Minor cxns from final proofread
1 parent 6f7eb0c commit e5f3931

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

articles/databox-online/azure-stack-edge-gpu-disconnected-scenario.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ ms.subservice: edge
99
ms.topic: conceptual
1010
ms.date: 02/24/2022
1111
ms.author: alkohli
12-
# Customer intent: As an IT admin, I need to understand how to use Azure Stack Edge with no internet connection to meet my organization's security restrictions.
12+
# Customer intent: As an IT admin, I need to understand how to use Azure Stack Edge with no internet connection to meet my organization's security restrictions.
1313
---
1414

1515
# Disconnected scenario for Azure Stack Edge
@@ -49,9 +49,9 @@ The following table describes the behavior of features and components when the d
4949
|------------------------------------|-----------------------------------|
5050
| Local UI and [Windows PowerShell interface](azure-stack-edge-gpu-connect-powershell-interface.md) | Local access via the local web UI or the Windows PowerShell interface is available by connecting a client computer directly to the device. |
5151
| [Kubernetes](azure-stack-edge-gpu-kubernetes-overview.md) | Kubernetes deployments on a disconnected device have these differences:<ul><li>After you create your Kubernetes cluster, you can connect to and manage the cluster locally from your device using a native tool such as `kubectl`. With `kubectl`, a `kubeconfig` file allows the Kubernetes client to talk directly to the Kubernetes cluster without connecting to PowerShell interface of your device. Once you have the config file, you can direct the cluster using `kubectl` commands, without physical access to the cluster. For more information, see [Create and Manage a Kubernetes cluster on an Azure Stack Edge Pro GPU device](azure-stack-edge-gpu-create-kubernetes-cluster.md).</li><li>Azure Stack Edge has a local container registry - the Edge container registry - to host container images. While your device is disconnected, you'll manage the deployment of these images, pushing them to and deleting them from the Edge container registry over your local network. You won't have direct access to the Azure Container Registry in the cloud. For more information, see [Enable an Edge container registry on an Azure Stack Edge Pro GPU device](azure-stack-edge-gpu-edge-container-registry.md).</li><li>You can't monitor the Kubernetes cluster using Azure Monitor. Instead, use the local Kubernetes dashboard, available on the compute network. For more information, see [Monitor your Azure Stack Edge Pro device via the Kubernetes dashboard](azure-stack-edge-gpu-monitor-kubernetes-dashboard.md).</li></ul>For more information, see [Kubernetes on your Azure Stack Edge Pro GPU device](azure-stack-edge-gpu-kubernetes-overview.md). |
52-
| [Azure Arc for Kubernetes](azure-stack-edge-gpu-deploy-arc-kubernetes-cluster.md) | An Azure Arc-enabled Kubernetes deployment can't be used in a disconnected deployment. |
53-
| [IoT Edge](azure-stack-edge-gpu-deploy-compute-module-simple.md) | IoT Edge modules need to be deployed and updated while connected to Azure. If disconnected from Azure, they continue to run. |
52+
| [Azure Arc on Kubernetes](azure-stack-edge-gpu-deploy-arc-kubernetes-cluster.md) | An Azure Arc-enabled Kubernetes deployment can't be used in a disconnected deployment. |
5453
| Azure Arc-enabled data services | After the container images are deployed on the device, Azure Arc-enabled data services continue to run in a disconnected deployment. You'll deploy and manage those images over your local network. You'll push images to and delete them from the Edge container registry. For more information, see [Manage container registry images](azure-stack-edge-gpu-edge-container-registry.md#manage-container-registry-images). |
54+
| [IoT Edge](azure-stack-edge-gpu-deploy-compute-module-simple.md) | IoT Edge modules need to be deployed and updated while connected to Azure. If disconnected from Azure, they continue to run. |
5555
| [Azure Storage access tiers](azure-stack-edge-gpu-deploy-add-shares.md) | During disconnected use:<ul><li>Data in your Azure Storage account won't be uploaded to and from access tiers in the Azure cloud.</li><li>Ghosted data can't be accessed directly through the device. Any access attempt fails with an error.</li><li>The Refresh option can't be used to sync data in your Azure Storage account with shares in the Azure cloud. Data syncs resume when connectivity is established.</li></ul> |
5656
| [VM management](azure-stack-edge-gpu-virtual-machine-overview.md) | During disconnected use, virtual machines can be created, modified, stopped, started, and deleted using the [local Azure Resource Manager (ARM)](azure-stack-edge-gpu-local-resource-manager-overview.md). However, VM images can't be downloaded to the device from the cloud. For more information, see [Deploy VMs on your Azure Stack Edge device via Azure PowerShell](azure-stack-edge-gpu-deploy-virtual-machine-powershell.md). |
5757
| [Local ARM](azure-stack-edge-gpu-local-resource-manager-overview.md) | Local Azure Resource Manager (ARM) can function without connectivity to Azure. However, connectivity is required during registration and configuration of Local ARM - for example, to [set the ARM Edge user password](azure-stack-edge-gpu-set-azure-resource-manager-password.md#reset-password-via-the-azure-portal) and ARM subscription ID. |

0 commit comments

Comments
 (0)