Importing Configuration into a Cluster

When running as a cluster, all Traffic Managers must have an identical copy of the configuration. When using the Configuration Importer, the Traffic Manager supports two alternative methods of ensuring the configuration of all cluster members remains consistent:

When an administrator makes a configuration change through the Admin UI or the REST API, they select a specific cluster member on which to make the change. The Traffic Manager then automatically replicates that change out to all other members of the cluster.

The Configuration Importer can also operate under the same principle. An administrator selects a cluster member on which to run the Configuration Importer, and the imported configuration is automatically replicated out to all other cluster members. When configuration is entirely managed through the Configuration Importer, you designate a single cluster member to watch for configuration changes and apply them to the whole cluster.

As an alternative, provided each Traffic Manager has access to the same configuration documents, you can instruct the Configuration Importer to not replicate configuration to the other cluster members. In this situation, each cluster member must maintain its own configuration independently.

For Docker deployments, to have each container independently manage its own configuration, launch the container with the ZEUS_CONFIG_IMPORT_ARGS environment variable set to "--no-replicate".

For other deployments, add the "--no-replicate" argument to the "config-import" tool when it is invoked. For example: