DC/OS 1.10.6 was released on April 24, 2018.
DC/OS 1.10.6 includes the following:
Issues Fixed in DC/OS 1.10.6
- COPS-2931/DCOS-21451/SOAK-68 - Fixed 404 error returned by adminrouter on Marathon UI/Prevented the reuse of tcp sockets by AR’s cache code.
- COPS-2931 - Fixed an error response that occurred when accessing DC/OS Services UI.
- CORE-1425 - Fixed launching nested containers to be more reliable.
- DCOS-19865 - Fixed focus/change/blur behavior.
- DCOS-22016 - Updated prometheus documentation with metrics in Prometheus.
- DCOS_OSS-2376 - Ensured that names cannot begin with numbers in Prometheus plugin.
Notable Changes in DC/OS 1.10.6
- COPS-1879/COPS-2166/DCOS_OSS-2315 - Bumped Mesos SHA to the latest 1.4.2-dev version. (changelog).
- CORE-1447/CORE-1448/CORE-1449 - Bumped version of dcos-ee-mesos-modules which included an update to the retry logic of the Mesos authorizer to better handle failed login attempts with the DC/OS IAM service. Enterprise
- DCOS-21683 - Bumped CockroachDB to version 1.1.7. Enterprise
- DCOS-21709 - Marathon supports preferential GPU scheduling on DC/OS.
- DCOS-16431 - Added short-lived Admin Router permission cache. Enabled by setting adminrouter_auth_cache_enabled: true in config.yaml. This option is disabled by default.
- DCOS_OSS-1903 - Upgraded
opensslfrom version 1.0.2k to 1.0.2n.
- DCOS_OSS-2181 - Bumped OpenResty to version 1.13.6.
- DCOS_OSS-2229 - Bumped Navstar.
- QUALITY-1525 - Support for Docker CE 17.03.0.
Note: DC/OS 1.10.6 release supports new CoreOS and Docker versions on RHEL listed in the compatibility matrix.
About DC/OS 1.10
DC/OS 1.10.0 includes many new capabilities for Operators and expands the collection of Data & Developer Services with a focus on:
- Core DC/OS service continuity - System resilience, IAM scalability & simplified upgrades.
- Robust security - Custom CA certificate & file-based secrets support. Enterprise
- Enterprise-ready networking - New DC/OS Edge-LB for higher availability and security. Enterprise
- Kubernetes is now available on DC/OS.
- Data services enhancements across the board.
- Rolling configuration update and upgrade support via the CLI. Enterprise
- Ability to deploy Data Services into folders to enable multi team deployments. Enterprise
- Ability to deploy to CNI-Based virtual networks.
Please try out the new features and updated data services. Provide any feedback through our support channel: support.mesosphere.com.
New Features and Capabilities
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.
Edge-LB load balancer. Enterprise
Edge-LB load balances Mesos tasks. Not supported in strict security mode. View the documentation.
Custom CA certificate support. Installation time configuration options have been added that allow you to configure DC/OS Enterprise to use a custom CA certificate and corresponding private key, which DC/OS then uses for issuing all component certificates. The custom CA certificate can be an intermediate CA certificate so that that all certificates used within the DC/OS cluster derive from your organization’s X.509 certification hierarchy.
Enhanced secrets management with file-based secrets. You can now make a secret available to your service in the sandbox of the task. View the documentation.
Vastly improved IAM scalability and performance characteristics. The new system removes hard limits on the number of users, groups, and permissions that can be stored, and shows stable read and write performance as the dataset grows.
pullConfigparameter. Use this parameter in your service definition to authenticate to a private Docker registry. View the documentation.
Enterprise CLI permissions management commands. It is now possible to manage permissions to protect resources using the DC/OS Enterprise CLI.
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
- Rolling Configuration Update and Upgrades support via the CLI. Enterprise
- Ability to deploy Data Services into Folders to enable multi team deployments. Enterprise
- Ability to deploy to CNI-Based Virtual Networks.
The following updated data services packages are compatible with DC/OS 1.10.0.
- 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 backup and restore, and pre/post flight checks. Enterprise
- 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.
- Scale and performance limits.
- DC/OS 1.10.0 requires DC/OS CLI 0.5.x.
- DC/OS CLI 0.5.x adds multi-cluster support with
Multi-cluster support has a number of consequences:
- 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
- DC/OS CLI 0.5.x introduces the
dcos cluster setupcommand to configure a connection to a cluster and log into the cluster.
- 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 setcommand, the command prints a warning message saying the command is deprecated and cluster configuration state may now be corrupted.
- If you have the
DCOS_CONFIGenvironment variable configured:
- After conversion to the new configuration structure,
DCOS_CONFIGis no longer honored.
- Before you call
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.
- After conversion to the new configuration structure,
- 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.
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 “Security” tab has been removed. The “Secrets” tab that used to be under “Security” is now a top-level tab. Enterprise
- The “Universe” tab has been renamed to “Catalog” and the “Installed” subpage has been removed.
- The “System Overview” tab has been renamed to “Overview”.
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.
TLS 1.0 is no longer enabled by default in Admin Router. Enterprise
TLS 1.0 no longer meets common minimum security requirements. To use TLS 1.0, set
config.yamlat install time. The default is
Moved file location for the DC/OS CA bundle in the sandbox of Mesos tasks from
$MESOS_SANDBOX/.ssl/ca-bundle.crtand declared the new file path to be stable.
Marathon-LB 1.11.0 or greater is required for DC/OS 1.10.0.
Before upgrading to DC/OS 1.10.0, uninstall your existing Marathon-LB package and reinstall the updated version.
REX-Ray configuration change.
DC/OS 1.10.0 upgrades REX-Ray from v0.3.3 to v0.9.0 and the REX-Ray configuration format has changed. If you have specified custom REX-Ray configuration in the
rexray_configparameter of your
config.yamlfile, either update the configuration to the new format or remove
rexray_configand set the parameter to
rexray_config_preset: aws, which configures the
rexray_configparameter to the default REX-Ray configuration bundled with DC/OS. This option has the benefit of automatically upgrading your cluster’s REX-Ray configuration when you upgrade to a newer version of DC/OS. Note: The
rexray_config_preset: awsoption is only relevant to DC/OS clusters running on AWS.
New flow to change the
dcos_urland log in.
The new command to set up your cluster URL is
dcos cluster setup <dcos_url>. For details, see CLI.
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 give more predictable performance across all tasks but might lead to a slowdown for tasks (and thereby also deployments) who have previously have consumed more CPU cycles than allocated. See MESOS-6134 for more details.
- 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.
- INFINITY-1809 - [Data Svc] DC/OS Service Update / Config Update / Maintenance. Enterprise
- MARATHON-7736 - Marathon Client Java library does NOT work with Marathon 1.5.