(DEPRECATED) DC/OS agent pools for Azure Container Service

  • Article

Warning

The Azure Container Service (ACS) is being deprecated. No new features or functionality are being added to ACS. All of the APIs, portal experience, CLI commands and documentation are marked as deprecated.

For more information, see the Azure Container Service deprecation announcement on Azure.com.

We recommend that you deploy one of the following Azure Marketplace solutions:

If you want to use Kubernetes, see Azure Kubernetes Service.

DC/OS clusters in Azure Container Service contain agent nodes in two pools, a public pool and a private pool. An application can be deployed to either pool, affecting accessibility between machines in your container service. The machines can be exposed to the internet (public) or kept internal (private). This article gives a brief overview of why there are public and private pools.

  • Private agents: Private agent nodes run through a non-routable network. This network is only accessible from the admin zone or through the public zone edge router. By default, DC/OS launches apps on private agent nodes.

  • Public agents: Public agent nodes run DC/OS apps and services through a publicly accessible network.

For more information about DC/OS network security, see the DC/OS documentation.

Deploy agent pools

The DC/OS agent pools In Azure Container Service are created as follows:

  • The private pool contains the number of agent nodes that you specify when you deploy the DC/OS cluster.

  • The public pool initially contains a predetermined number of agent nodes. This pool is added automatically when the DC/OS cluster is provisioned.

The private pool and the public pool are Azure virtual machine scale sets. You can resize these pools after deployment.

Use agent pools

By default, Marathon deploys any new application to the private agent nodes. You have to explicitly deploy the application to the public nodes during the creation of the application. Select the Optional tab and enter slave_public for the Accepted Resource Roles value. This process is documented here and in the DC/OS documentation.

Next steps