Contents

New Features and Capabilities

Apache Mesos 1.4 and Marathon 1.5 Integrated.

DC/OS 1.10 is is based on Mesos 1.4.0, here using master branch (pre-release) SHA 013f7e21, with over 1200 commits since the previous Mesos version. View the changelog.

DC/OS 1.10 is integrated with the latest release of Marathon, version 1.5. Resulting breaking changes and new features are documented below. For more information about Marathon 1.5, consult the Marathon changelog.

Networking

Configurable Spartan upstreams for domains (dnames).
You can now configure Spartan to delegate a particular domain (e.g. "*.foo.company.com") to a particular upstream.

Platform

Node and Cluster health checks.
Write your own custom health checks or use the predefined checks to access and use information about your cluster, including available ports, Mesos agent status, and IP detect script validation. View the documentation.

Enhanced upgrades with pre/post flight checks.

Universal Container Runtime (UCR).
Adds port mapping support for containers running on the CNI network. Port mapping support allows UCR to have a default bridge network, similar to Docker's default bridge network. This gives UCR feature parity with Docker Engine enabling use of Mesos Runtime as the default container runtime. View the documentation.

Scale and performance limits.

CLI

DC/OS CLI 0.4.x and 0.5.x use a different structure for the location of configuration files. DC/OS CLI 0.4.x has a single configuration file, which by default is stored in ~/.dcos/dcos.toml. DC/OS CLI 0.5.x has a configuration file for each connected cluster, which by default are stored in ~/.dcos/clusters/<cluster_id>/dcos.toml.

DC/OS CLI 0.5.x introduces the dcos cluster setup command to configure a connection to a cluster and log into the cluster.

Note:

Updating to the DC/OS CLI 0.5.x and running any CLI command triggers conversion from the old to the new configuration structure.

After you call dcos cluster setup, (or after conversion has occurred), if you attempt to update the cluster configuration using a dcos config set command, the command prints a warning message saying the command is deprecated and cluster configuration state may now be corrupted.

If you have the DCOS_CONFIG environment variable configured:

After conversion to the new configuration structure, DCOS_CONFIG is no longer honored.

Before you call dcos cluster setup, you can change the configuration pointed to by DCOS_CONFIG using dcos config set. This command prints a warning message saying the command is deprecated and recommends using dcos cluster setup.

CLI modules are cluster-specific and stored in ~/.dcos/clusters/<cluster_id>/subcommands. Therefore you must install a CLI module for each cluster. For example, if you connect to cluster 1, and install the Spark module, then connect to cluster 2 which is also running Spark, Spark CLI commands are not available until you install the module for that cluster.

GUI

The GUI sidebar tabs have been updated to offer a more intuitive experience.

The "Deployments" subpage under the "Services" tab has been moved to a toggle-able modal in the "Services" page.

The "Universe" tab has been renamed to "Catalog" and the "Installed" subpage has been removed.

The "System Overview" tab has been renamed to "Overview".

Kubernetes on DC/OS

Kubernetes on DC/OS is beta with DC/OS 1.10.0. Install from the DC/OS Service Catalog or use the quickstart.

Updated DC/OS Data Services

Ability to deploy Data Services into Folders to enable multi team deployments.

Ability to deploy to CNI-Based Virtual Networks.

The following updated data services packages are compatible with DC/OS 1.10.

Breaking Changes

Marathon Networking API Changes in 1.5.

The networking section of the Marathon API has changed significantly in version 1.5. Marathon can still accept requests using the 1.4 version of the API, but it will always reply with the 1.5 version of the app definition. This will break tools that consume networking-related fields of the service definition. View the documentation.

The latest version of Marathon-LB is required for 1.10.

Before upgrading to 1.10, uninstall your existing Marathon-LB package and reinstall the updated version. See the upgrade section for more information.

REX-Ray configuration change.

DC/OS 1.10 upgrades REX-Ray from v0.3.3. to v0.9.0 and therefore the REX-Ray configuration format has changed. If you have specified custom REX-Ray configuration in the REX-Ray_config parameter of your config.yaml file, change the parameter to REX-Ray_config_preset: aws.

New flow to change the dcos_url and login.

The new command to change your cluster URL is dcos cluster setup <dcos_url>. This change will break any existing tooling that uses the former command. Backwards compatibility is slated for a future patch release.

Hard CFS CPU limits enabled by default.

DC/OS 1.10 enforces hard CPU limits with CFS isolation for both the Docker and Universal Container Runtimes. This will provide more predictable performance across all tasks, but might lead to a slowdown for tasks (and also deployments) that had previously consumed more CPU cycles than allocated.
See MESOS-6134 for more details.

Known Issues and Limitations

Upgrade: During upgrade to DC/OS 1.10, there is a brief moment when the DNS resolution does not work. If a health check runs at that moment, it will fail and services will be reported as unhealthy.

CORE-1125 - Docker image pull config is re-used.

DCOS-16547 - Task state does not update after the agent running it was removed from the cluster.

MARATHON-7736 - Marathon Client Java library does NOT work with Marathon 1.5.