Mesosphere® DC/OS™ 2.1.0 was released on 9, June 2020.
New customers must contact your sales representative or firstname.lastname@example.org before attempting to download and install DC/OS Enterprise.
DC/OS is a distributed operating system that enables you to manage resources, application deployment, data services, networking, and security in an on-premise, cloud, or hybrid cluster environment.
This release provides new features and enhancements to improve the user experience, fix reported issues, integrate changes from previous releases, and maintain compatibility and support for other packages, such as Marathon and Metronome, used in DC/OS.
New Features and Capabilities
Vertical Container Bursting
DC/OS now allows you to set a limit on the amount of CPUs and memory used by Marathon apps and pods. This means that services can run with a guaranteed amount of CPU and memory, while being allowed to consume up to a greater amount of these resources when free CPU cycles and/or memory is available. For more information, see Creating Services.
Network Policies with Calico
Calico is now pre-installed in DC/OS 2.1 and can be used by containers to join overlay networks and set network policies. The DC/OS Calico component integrates Calico networking into DC/OS, providing the Calico CNI plug-in for Mesos Universal Container Runtime and the Calico libnetwork plug-in for Docker Engine. For more information, see Calico.
Jobs Virtual Networking Support
Metronome based jobs can now join container networks to communicate with other services/jobs in the same network. For more information, see Creating Jobs.
Custom Certificates for Admin Router
DC/OS now allows you to provide a non-CA custom external certificate and key that the Admin Router will then use for clients connecting to a cluster. For more information, see Configuring a Custom External Certificate
Domain Sockets for Agent Executor Communication
Added a new configuration option
mesos_http_executors_domain_sockets, which will cause the mesos-agent to use domain sockets when communicating with executors (default is enabled). This change allows administrators to write firewall rules blocking unauthorized access to the agent port 5051 since access to this will not be required anymore for executors to work.
Docker Hub announced an update to their image pull policies in August 2020. The change results in the need to change cluster configurations to accommodate new account structures that enable image pull rate limiting.
Rate limiting happens on a per-pull basis regardless of whether the pulled image is owned by a paid user. This means D2iQ, as owner of most images used in Mesosphere® DC/OS®, does not have any influence as to whether your current address is rate-limited or not. Mesosphere DC/OS does not have a strict dependency on Docker Hub accounts or plans.
Without any further configuration, your cluster is likely using the “Free plan - anonymous users” tier. This means that if each of your nodes has its own public IP address, you can do 100 image pulls per 6 hours on every node. While this should not be a problem with just a few, usually-healthy workloads, but you may encounter unforeseeable issues if you:
- Have constantly failing tasks
- Are running a large number of CI jobs
- Have metronome tasks with different containers
- Use the docker.forcePullImage option
In the worst case, your cluster might not be able to reschedule a failed task for up to 6 hours, which could lead to unresponsive services or even data corruption, for example, when using clustered databases.
The DC/OS software offers several ways to specify these credentials:
Cluster-wide credentials using dcos-config.yml: Using Docker credentials to set cluster-wide registry credentials
Task-specific credentials using secrets: Reference private docker registry credentials in DC/OS secrets
A non-DC/OS-specific way to specify the Docker credentials is to use the .docker/config.json file on each agent, as described here: Create a Docker credentials configuration file
The configuration option
MARATHON_ACCEPTED_RESOURCE_ROLES_DEFAULT_BEHAVIORreplaces the config option
MARATHON_DEFAULT_ACCEPTED_RESOURCE_ROLES. Please see the Marathon command-line flag documentation for a description of the flag.
Marathon no longer sanitizes the field
acceptedResourceRoles. The field is an array of one or two values:
*and the service role. Previously, when an invalid value was provided, Marathon would silently drop it. Now, it returns an error. If this causes a disruption, you can re-enable this feature by adding
MARATHON_DEPRECATED_FEATURES=sanitize_accepted_resource_rolesto the file
/var/lib/dcos/marathon/environmenton all masters. You must remove this line before upgrading to the next version of DC/OS.
DC/OS Net now waits until agents become active before adding DNS entries for tasks on the agent to prevent resolving to unreachable addresses. (DCOS_OSS-5463)
dcos-net (l4lb) allows for graceful shutdown of connections by changing the VIP backend weight to 0 when tasks are unhealthy or enter the TASK_KILLING state instead of removing them. (D2iQ-61077)
Removed the spartan package from DC/OS. Is was deprecated in 1.11 and replaced by dcos-net.
Removed the toybox package from DC/OS. Is was used only by Spartan.
Removed the dcos-history-service from DC/OS. (DCOS-58529)
New format for Admin Router access logs. (D2iQ-43957, DCOS-59598, D2iQ-62839)
DC/OS 2.1.0 includes the following component versions:
- Apache® Mesos® 1.10.0-dev
- Marathon 1.10.17
- Metronome 0.6.44
- DC/OS UI to v5.0.41
Fixed and Improved Issues
- Zookeeper log messages are now being forwarded to syslog. (COPS-6128)
- Fixed a critical error in Metronome where existing jobs appear to be lost after upgrade. (COPS-6092)
- (COPS-5951, COPS-5827)
- Fixed an issue where in some rare circumstances, after upgrading a cluster, users were no longer able to launch tasks that use the UCR containerizer. (D2iQ-64507, COPS-5868)
- Fixed an issue where image pull in UCR was not working for nvcr.io (missing ‘service’/‘scope’ parameters). (COPS-5804)
- Upgraded Java to version 8u232 to align with previous DC/OS releases. (DCOS-62548, COPS-5738)
- Fixed an issue where after a DC/OS upgrade, the executor resources used by tasks on the agent were being incorrectly counted against quota. (COPS-5725)
- DC/OS Admin Router now allows large packages of files, up to 32GB, to the Package Registry. (D2iQ-61233, COPS-5615)
- Additional logging has been added to the installation scripts to aid in debugging installation issues. (COPS-5428)
- Fixed an issue where the Mesos master crashed in some situations if an agent was drained and then subsequently reactivated. (COPS-5931, MESOS-10116)
- The dcos-diagnostics component now rate limits diagnostic checks to avoid performance slowdowns in large clusters. (COPS-5915)
- A dcos-cosmos template engine can now accept unescaped raw JSON fields. (COPS-5814)
- The dcos-telegraf component has been enhanced to allow configuration of the allowed_pending_messages parameter. (COPS-5629)
- Removed the octarine package from DC/OS.
- Removed the avro-cpp package from DC/OS.
Mesos Fixed and Improved Issues
For a detailed description on updates to Mesos, see the changelog
Marathon Fixed and Improved Issues
For a detailed description on updates to Marathon, see the changelog.
Metronome Fixed and Improved Issues
For a detailed description on updates to Metronome, see the changelog.