Skip to content
forked from Azure/acs-engine

Azure Container Service Engine - a place for community to collaborate and build the best open Docker container infrastructure for Azure.

License

Notifications You must be signed in to change notification settings

bhope/acs-engine

This branch is 1129 commits behind Azure/acs-engine:master.

Folders and files

NameName
Last commit message
Last commit date
Jan 6, 2018
Jul 10, 2017
Jan 16, 2018
Feb 1, 2018
Jan 25, 2018
Feb 1, 2018
Jan 9, 2018
Dec 27, 2017
Jan 26, 2018
Jan 31, 2018
Nov 1, 2017
Jan 6, 2018
Jan 26, 2018
Jan 10, 2018
Jan 11, 2018
Nov 7, 2017
Aug 10, 2017
Oct 27, 2016
Oct 11, 2017
Oct 9, 2017
Nov 1, 2017
Nov 3, 2017
Oct 6, 2016
Nov 7, 2017
May 19, 2017
Aug 3, 2017
Aug 3, 2017
Jan 11, 2018
Jan 11, 2018
Jul 11, 2017
Aug 23, 2017
Nov 7, 2017
Aug 25, 2017

Repository files navigation

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/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 [email protected] with any additional questions or comments.

About

Azure Container Service Engine - a place for community to collaborate and build the best open Docker container infrastructure for Azure.

Resources

License

Stars

Watchers

Forks

Packages

No packages published

Languages

  • Go 68.0%
  • Other 16.5%
  • Shell 7.6%
  • Perl 3.1%
  • PowerShell 2.6%
  • Groovy 1.5%
  • Other 0.7%