readme typo (#262)
This commit is contained in:
committed by
Robbie Zhang
parent
ae79bb5216
commit
a3bd10ab5f
@@ -1,6 +1,6 @@
|
||||
# Kubernetes Virtual Kubelet with Azure Batch
|
||||
|
||||
[Azure Batch](https://docs.microsoft.com/en-us/azure/batch/) provides a HPC Computing environment in Azure for distributed tasks. Azure Batch handles scheduling decrete jobs and tasks accross pools of VM's. It is commonly used for batch processing tasks such as rendering.
|
||||
[Azure Batch](https://docs.microsoft.com/en-us/azure/batch/) provides a HPC Computing environment in Azure for distributed tasks. Azure Batch handles scheduling of discrete jobs and tasks accross pools of VM's. It is commonly used for batch processing tasks such as rendering.
|
||||
|
||||
The Virtual kubelet integration allows you to take advantage of this from within Kubernetes. The primary usecase for the provider is to make it easy to use GPU based workload from normal Kubernetes clusters. For example, creating Kubernetes Jobs which train or execute ML models using Nvidia GPU's or using FFMPEG.
|
||||
|
||||
@@ -76,4 +76,4 @@ The provider expects the following environment variables to be configured:
|
||||
The provider will assign pods to machines in the Azure Batch Pool. Each machine can, by default, process only one pod at a time
|
||||
running more than 1 pod per machine isn't currently supported and will result in errors.
|
||||
|
||||
Azure Batch queues tasks when no machines are available so pods will sit in `podPending` state while waiting for a VM to become available.
|
||||
Azure Batch queues tasks when no machines are available so pods will sit in `podPending` state while waiting for a VM to become available.
|
||||
|
||||
Reference in New Issue
Block a user