Azure Container Instances supports Linux containers in three new regions: Australia East (New South Wales), East US 2 (Virginia), and Central US (Iowa). These additions bring the total to nine regions across the globe.
Azure Container Instances supports multiple new features in the release of the June API 01-06-2018 including multiple container groups per single YAML, secrets can now be passed in environment variables, liveness probes and more.
Azure Container Instances now includes support for running containerized tasks. Here are the updates for February 2018:
DNS name labels for containers: Configure a reliable endpoint for each container by placing a DNS name label through the REST API or Azure CLI 2.0.
az container create --resource-group MyResourceGroup --name myalpine --image alpine:latest --ports 80 443 --dns-name-label contoso
Streaming container logs with Azure CLI 2.0: Read your container state and log output by attaching to your container from Azure CLI 2.0.
az container attach --resource-group MyResourceGroup --name myalpine
Container restart policies: Designate containers to always restart, restart only on failure, or never restart.
Various volume types for mounting: Mount Azure Files, gitRepo, emptyDir, and secret volumes.
Guidance on container failures: Error messages provided for container instance failures have been refined and extended to improve self-debugging.
Support for the Southeast Asia region: Deploy container instances from Southeast Asia in addition to East US, West US, and West Europe.