Azure Container Service Engine - a place for community to collaborate and build the best open Docker container infrastructure for Azure.
Go Perl 6 Shell Perl PowerShell Groovy Other
Latest commit cda9631 Dec 15, 2017 @jackfrancis jackfrancis X crypto (#1943)
* pin x/crypto to older version, and freshen vendor/ otherwise

* straggler
Failed to load latest commit information.
.circleci pin docker version swarm (#1848) Nov 29, 2017
.github docs(github): include acs-engine version in issue template (#943) Jul 10, 2017
cmd JSON serialization with optional HTML escaping (#1876) Dec 5, 2017
docs Update (#1920) Dec 12, 2017
examples add new connector (#1927) Dec 14, 2017
extensions fix race condition bug with kubectl returning nodes (#1889) Dec 6, 2017
loc LEGO: check in for master to temporary branch. (#1610) Oct 20, 2017
parts add new connector (#1927) Dec 14, 2017
pkg more general vlabs kubernetes defaults enforcement (#1932) Dec 14, 2017
releases Add support to build official Docker image from release binaries. (#1659 Nov 1, 2017
scripts Update build script for v1.8 (#1866) Dec 1, 2017
test compare as strings (#1923) Dec 12, 2017
translations Add script to convert LCL to PO and generate PO files (#1344) Aug 24, 2017
vendor X crypto (#1943) Dec 15, 2017
windows Switch to RS3 Windows in Kubernetes cluster (#1686) Nov 7, 2017
.dockerignore Fix make generate slowness on Docker for Mac (#1226) Aug 10, 2017
.gitattributes Add devenv for building/testing/validating under Docker Oct 27, 2016
.gitignore Etcd3 Support (#1564) Oct 11, 2017 remove duplicate sentence (#1559) Oct 9, 2017
Dockerfile Update AZ CLI to latest (#1698) Nov 1, 2017
Dockerfile.k8swin Dev environment setup for k8s on Windows machine (#1703) Nov 3, 2017
LICENSE Add License Oct 6, 2016
Makefile fix( remove the date string from the header Nov 7, 2017
OWNERS PROPOSAL: version numbering scheme using SemVer 2.0 (#642) May 19, 2017 ref(docs): reorganize documentation Aug 3, 2017 ref(docs): reorganize documentation Aug 3, 2017
glide.lock X crypto (#1943) Dec 15, 2017
glide.yaml X crypto (#1943) Dec 15, 2017
labels.yaml docs(github): use labeler to manage project labels (#955) Jul 11, 2017
main.go vendor/ dependency rationalization (#1340) Aug 23, 2017 fix( remove the date string from the header Nov 7, 2017 version output improvements (#1325) Aug 25, 2017

Microsoft Azure Container Service Engine - Builds Docker Enabled Clusters

Coverage Status CircleCI


The Azure Container Service Engine (acs-engine) generates ARM (Azure Resource Manager) templates for Docker enabled clusters on Microsoft Azure with your choice of DC/OS, Kubernetes, Swarm Mode, or Swarm orchestrators. The input to the tool is a cluster definition. The cluster definition is very similar to (in many cases the same as) the ARM template syntax used to deploy a Microsoft Azure Container Service cluster.

The cluster definition file enables the following customizations to your Docker enabled cluster:

  • choice of DC/OS, Kubernetes, Swarm Mode, or Swarm orchestrators
  • multiple agent pools where each agent pool can specify:
  • standard or premium VM Sizes,
  • node count,
  • Virtual Machine ScaleSets or Availability Sets,
  • Storage Account Disks or Managed Disks (under private preview)
  • Docker cluster sizes of 1200
  • Custom VNET

User guides


Please follow these instructions before submitting a PR:

  1. Execute make ci to run the checkin validation tests.

  2. Manually test deployments if you are making modifications to the templates. For example, if you have to change the expected resulting templates then you should deploy the relevant example cluster definitions to ensure you're not introducing any sort of regression.


Generate Templates

Usage is best demonstrated with an example:

$ vim examples/kubernetes.classic.json

# insert your preferred, unique DNS prefix
# insert your SSH public key

$ ./acs-engine generate examples/kubernetes.classic.json

This produces a new directory inside _output/ that contains an ARM template for deploying Kubernetes into Azure. (In the case of Kubernetes, some additional needed assets are generated and placed in the output directory.)

Code of conduct

This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact with any additional questions or comments.