DC/OS 1.10 includes many new capabilities for Operators and expands the collection of Data & Developer Services with a focus on:
Please try out the new features and updated data services. Provide any feedback through Jira: https://jira.dcos.io.
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.
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.
Increased CNI network support. DC/OS now supports any type of CNI network. View the documentation.
~/.dcos/dcos.toml. DC/OS CLI 0.5.x has a configuration file for each connected cluster, which by default are stored in
dcos cluster setupcommand to configure a connection to a cluster and log into the cluster.
dcos cluster setup, (or after conversion has occurred), if you attempt to update the cluster configuration using a
dcos config setcommand, the command prints a warning message saying the command is deprecated and cluster configuration state may now be corrupted.
DCOS_CONFIGenvironment variable configured:
DCOS_CONFIGis no longer honored.
dcos cluster setup, you can change the configuration pointed to by
dcos config set. This command prints a warning message saying the command is deprecated and recommends using
dcos cluster setup.
~/.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.
The GUI sidebar tabs have been updated to offer a more intuitive experience.
The following updated data services packages are compatible with DC/OS 1.10.
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
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.
DockerContainerizerif network mode is "NONE".