Microsoft Azure Container Service Engine - Builds Docker Enabled Clusters

Overview

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 (or apimodel) 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 you to customize your Docker enabled cluster in many ways including:

choice of DC/OS, Kubernetes, Swarm Mode, or Swarm orchestrators
multiple agent pools where each agent pool can specify:
- standard or premium VM Sizes, including GPU optimized VM sizes
- node count
- Virtual Machine ScaleSets or Availability Sets
- Storage Account Disks or Managed Disks
- OS and distro
Custom VNET
Extensions

User guides

ACS Engine - shows you how to build and use the ACS engine to generate custom Docker enabled container clusters
Cluster Definition - describes the components of the cluster definition file
DC/OS Walkthrough - shows how to create a DC/OS enabled Docker cluster on Azure
Kubernetes Walkthrough - shows how to create a Kubernetes enabled Docker cluster on Azure
Swarm Walkthrough - shows how to create a Swarm enabled Docker cluster on Azure
Swarm Mode Walkthrough - shows how to create a Swarm Mode cluster on Azure
Custom VNET - shows how to use a custom VNET
Attached Disks - shows how to attach up to 4 disks per node
Managed Disks - shows how to use managed disks
Large Clusters - shows how to create cluster sizes of up to 1200 nodes

Contributing

Follow the developers guide to set up your environment.

To build acs-engine, run make build. If you are developing with a working Docker environment, you can also run make dev first to start a Docker container and run make build inside the container.

Please follow these instructions before submitting a PR:

Execute make test to run unit tests.
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 that you are not introducing any regressions.
Make sure that your changes are properly documented and include relevant unit tests.

Usage

Generate Templates

Usage is best demonstrated with an example:

$ vim examples/classic/kubernetes.classic.json

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

$ ./acs-engine generate examples/classic/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 opencode@microsoft.com with any additional questions or comments.