Skip to content
Azure Container Service Engine - a place for community to collaborate and build the best open Docker container infrastructure for Azure.
Branch: master
Clone or download
Pull request Compare This branch is 47 commits ahead, 913 commits behind Azure:master.
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
.circleci
.github
cmd
docs
examples
extensions
jenkins
loc
parts
pkg
releases
scripts
test
translations
vendor
windows
.dockerignore
.gitattributes
.gitignore
CONTRIBUTING.md
Dockerfile
Dockerfile.k8swin
LICENSE
Makefile
OWNERS
README.md
README_zh-CN.md
glide.lock
glide.yaml
labels.yaml
main.go
test.mk
versioning.mk

README.md

Microsoft Azure Container Service Engine - Builds Docker Enabled Clusters

Coverage Status CircleCI

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 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

Contributing

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.

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.

You can’t perform that action at this time.