Introducing DC/OS 1.8 GA!
For more than five years, DC/OS has enabled some of the largest, most sophisticated enterprises in the world to achieve unparalleled levels of efficiency, reliability, and scalability from their IT infrastructure. But now it is time to pass the torch to a new generation of technology: the D2iQ Kubernetes Platform (DKP). Why? Kubernetes has now achieved a level of capability that only DC/OS could formerly provide and is now evolving and improving far faster (as is true of its supporting ecosystem). That’s why we have chosen to sunset DC/OS, with an end-of-life date of October 31, 2021. With DKP, our customers get the same benefits provided by DC/OS and more, as well as access to the most impressive pace of innovation the technology world has ever seen. This was not an easy decision to make, but we are dedicated to enabling our customers to accelerate their digital transformations, so they can increase the velocity and responsiveness of their organizations to an ever-more challenging future. And the best way to do that right now is with DKP.
On behalf of the DC/OS community and the team at Mesosphere, I'm super excited to let you know that DC/OS 1.8 is in General Availability starting today! This release contains a ton of new open source features, and in case you haven't had a chance to try them out and contribute comments in any of the EA releases, below you'll find a summary of some of the highlights. They include: integrating Marathon and scheduled job support into the DC/OS user interface, upgrading to Mesos 1.0 which provides access to Universal Container Runtime, and Virtual Networks using CNI specs.
You might notice something new in our documentation starting with DC/OS 1.8: feature maturity tags that tell you how mature and stable a feature is. We're just rolling these out, so if you have feedback on them, please let us know. And of course feel free to contribute comments or code, especially to experimental and preview features. This release contains features with every maturity tag: experimental, preview, and stable; check out the documentation for each feature to get details.
Mesos 1.0 and the Universal Container Runtime
With 1.8, DC/OS now uses Mesos 1.0 (released in July; notes here), which includes new support for deploying Docker images using the Universal Container Runtime. The Universal Container Runtime lets users take advantage of existing and future Apache Mesos & DC/OS capabilities, including IP per container with CNI support, file-system isolation, and GPU support.
The integration of the Universal Container Runtime's deployment capabilities into DC/OS is experimental. It will give DC/OS users the option to deploy Docker containers with the native Mesos container engine, rather than with the Docker daemon (which will still be available). Please give this feature a try, and feel free to give us feedback or squash some bugs yourself; contributions are welcome!
Access Marathon through "DC/OS Services"
Marathon manages most DC/OS workloads, including stateless containers; Cassandra, Kafka, and HDFS service schedulers; and other long-running services like Java applications. Marathon has been a cornerstone of DC/OS since DC/OS version 1.0, and switching between the Marathon and DC/OS user interfaces has been clunky. With DC/OS 1.8, users don't need to take the extra steps to switch UIs. Instead Marathon is accessible as an integrated part of the DC/OS UI.
Built-in DC/OS Scheduled Jobs
We are also bringing native job scheduling capabilities into DC/OS through a new built-in feature, intuitively called "DC/OS Jobs". Much like what we did for DC/OS Services, you can access DC/OS Jobs from the DC/OS user interface. Don't forget that you can still install and launch Chronos through the DC/OS Universe! We would love for our users who depend on Chronos to switch over to Jobs, and are happy to help out on the mailing list or Slack with any migration questions.
IP per Container with Virtual Networks
DC/OS Virtual Networks leverage the Container Network Interface (CNI) standard, and support the creation of multiple virtual networks during the installation process (one, called ‘dcos', comes built in by default). Every container can now have its own IP address in DC/OS 1.8, because any container that attaches to a virtual network is assigned its own dedicated IP address.
We know a lot of people are excited about the new features in 1.8, including the experimental ones. If you're one of those excited people, please consider participating in the community! You can get involved by downloading 1.8 here, reading the release notes, filing any bugs you find, checking out the code and, if you find something you want to take on, opening up a PR! If you run into difficulties, or just want to chat, we look forward to seeing you on the mailing list or Slack.