Edit

Azure Stack Edge Pro with GPU Preview release notes

  • Article

APPLIES TO: Yes for Pro GPU SKUAzure Stack Edge Pro - GPU                  

The following release notes identify the critical open issues and the resolved issues for 2008 preview release for your Azure Stack Edge Pro devices with GPU.

The release notes are continuously updated, and as critical issues requiring a workaround are discovered, they are added. Before you deploy your Azure Stack Edge Pro device, carefully review the information contained in the release notes.

This article applies to the following software release - Azure Stack Edge Pro 2008.

What's new

The following new features were added in Azure Stack Edge 2008 release. Depending on the specific preview software version you are running, you may see a subset of these features.

  • Storage classes - In the previous release, you could only statically provision storage via SMB or NFS shares for stateful applications deployed on the Kubernetes cluster running on your Azure Stack Edge Pro device. In this release, Storage classes were added that let dynamically provision storage. For more information, see Kubernetes storage management on your Azure Stack Edge Pro GPU device.
  • Kubernetes dashboard with metrics server - In this release, a Kubernetes Dashboard is added with a metrics server add-on. You can use the dashboard to get an overview of the applications running on your Azure Stack Edge Pro device, view status of Kubernetes cluster resources, and see any errors that have occurred on the device. The Metrics server aggregates the CPU and memory usage across Kubernetes resources on the device. For more information, see Use Kubernetes dashboard to monitor your Azure Stack Edge Pro GPU device.
  • Azure Arc for Azure Stack Edge Pro - Beginning this release, you can deploy application workloads on your Azure Stack Edge Pro device via Azure Arc. Azure Arc is a hybrid management tool that allows you to deploy applications on your Kubernetes clusters. For more information, see Deploy workloads via Azure Arc on your Azure Stack Edge Pro device.

Known issues

The following table provides a summary of known issues for the Azure Stack Edge Pro device.

No. Feature Issue Workaround/comments
1. Azure Stack Edge Pro + Azure SQL Creating SQL database requires Administrator access. Do the following steps instead of Steps 1-2 in Tutorial: Store data at the edge with SQL Server databases.
  • In the local UI of your device, enable compute interface. Select Compute > Port # > Enable for compute > Apply.
  • Download sqlcmd utility on your client machine.
  • Connect to your compute interface IP address (the port that was enabled), adding a ",1401" to the end of the address.
  • Final command will look like this: sqlcmd -S {Interface IP},1401 -U SA -P "Strong!Passw0rd".
    • After this, steps 3-4 from the current documentation should be identical.
2. Refresh Incremental changes to blobs restored via Refresh are NOT supported For Blob endpoints, partial updates of blobs after a Refresh, may result in the updates not getting uploaded to the cloud. For example, sequence of actions such as:
  • Create blob in cloud. Or delete a previously uploaded blob from the device.
  • Refresh blob from the cloud into the appliance using the refresh functionality.
  • Update only a portion of the blob using Azure SDK REST APIs.
These actions can result in the updated sections of the blob to not get updated in the cloud.
Workaround: Use tools such as robocopy, or regular file copy through Explorer or command line, to replace entire blobs.
3. Throttling During throttling, if new writes are not allowed into the device, writes done by NFS client fail with "Permission Denied" error. The error will show as below:
hcsuser@ubuntu-vm:~/nfstest$ mkdir test
mkdir: cannot create directory 'test': Permission denied​
4. Blob Storage ingestion When using AzCopy version 10 for Blob storage ingestion, run AzCopy with the following argument: Azcopy <other arguments> --cap-mbps 2000 If these limits are not provided for AzCopy, then it could potentially send a large number of requests to the device and result in issues with the service.
5. Tiered storage accounts The following apply when using tiered storage accounts:
  • Only block blobs are supported. Page blobs are not supported.
  • There is no snapshot or copy API support.
  • Hadoop workload ingestion through distcp is not supported as it uses the copy operation heavily.
6. NFS share connection If multiple processes are copying to the same share, and the nolock attribute is not used, you may see errors during the copy.​ The nolock attribute must be passed to the mount command to copy files to the NFS share. For example: C:\Users\aseuser mount -o anon \\10.1.1.211\mnt\vms Z:.
7. Kubernetes cluster When applying an update on your device that is running a kubernetes cluster, the kubernetes virtual machines will restart and reboot. In this instance, only pods that are deployed with replicas specified are automatically restored after an update. If you have created individual pods outside of a replication controller without specifying a replica set, then these pods will not be automatically restored after the device update. You will need to restore these pods.
A replica set replaces pods that are deleted or terminated for any reason, such as node failure or disruptive node upgrade. For this reason, we recommend that you use a replica set even if your application requires only a single pod.
8. Kubernetes cluster Kubernetes on Azure Stack Edge Pro is supported only with Helm v3 or later. For more information, go to Frequently asked questions: Removal of Tiller.
9. Azure Arc + Azure Stack Edge Pro Azure Arc deployments are not supported if web proxy is configured on your Azure Stack Edge Pro device.
10. Kubernetes Port 31000 is reserved for Kubernetes Dashboard. Similarly, in the default configuration, the IP addresses 172.28.0.1 and 172.28.0.10, are reserved for Kubernetes service and Core DNS service respectively. Do not use reserved IPs.
11. Kubernetes Kubernetes does not currently allow multi-protocol LoadBalancer services. For example, a DNS service that would have to listen on both TCP and UDP. To work around this limitation of Kubernetes with MetalLB, two services (one for TCP, one for UDP) can be created on the same pod selector. These services use the same sharing key and spec.loadBalancerIP to share the same IP address. IPs can also be shared if you have more services than available IP addresses.
For more information, see IP address sharing.
12. Kubernetes cluster Existing Azure IoT Edge marketplace modules will not run on the Kubernetes cluster as the hosting platform for IoT Edge on Azure Stack Edge device. The modules will need to be modified before these are deployed on the Azure Stack Edge device. For more information, see Modify Azure IoT Edge modules from marketplace to run on Azure Stack Edge device.
13. Kubernetes File-based bind mounts are not supported with Azure IoT Edge on Kubernetes on Azure Stack Edge device. IoT Edge uses a translation layer to translate ContainerCreate options to Kubernetes constructs. Creating Binds maps to hostpath directory or create and thus file-based bind mounts cannot be bound to paths in IoT Edge containers.
14. Kubernetes If you bring your own certificates for IoT Edge and add those on your Azure Stack Edge device, the new certificates are not picked up as part of the Helm charts update. To workaround this problem, Connect to the PowerShell interface of the device. Restart iotedged and edgehub pods.
15. Certificates In certain instances, certificate state in the local UI may take several seconds to update. The following scenarios in the local UI may be affected.
  • Status column in Certificates page.
  • Security tile in Get started page.
  • Configuration tile in Overview page.

Next steps