We’ve just released Rancher v1.6, the latest version of our container management platform. While we still recommend that production or mission-critical deployments use our most recent stable release, we’re excited to share what’s new in v1.6. In this release, we’ve built greater control for our users over their storage and secrets.
Validating EBS Support
We first implemented support for EBS before Rancher itself was even generally available, but in v1.6, we’re removing the ‘experimental’ tag. In addition to fixing some minor issues flagged by our community, this release contains:
Availability-zone aware scheduling for better container management within the same AZ
Additional options for EBS volumes: now users can specify options like volumetype, encrypted, and snapshotltd
Consider our EBS support ready for production!
As a side note, Rancher EBS support and development of Project Longhorn should not be considered conflicting efforts – we will always support popular and leading technologies, AWS included. While Project Longhorn is slated for eventual inclusion into Rancher, it’s still experimental, and for now Longhorn and Rancher remain separate. Read more
As one of the most disruptive technologies in recent years, container-based applications are rapidly gaining traction as a platform on which to launch applications. But as with any new technology, the security of containers in all stages of the software lifecycle must be our highest priority. This post seeks to identify some of the inherent security challenges you’ll encounter with a container environment, and suggests base elements for a security plan to mitigate those vulnerabilities.
Benefits of a Container Environment and the Vulnerabilities They Expose
Before we investigate what aspects of your container infrastructure will need to be covered by your security plan, it would be wise to identify what potential security problems running applications in such an environment will present. The easiest way to do this is to contrast a typical virtual machine (VM) environment with that in use for a typical container-based architecture. Read more
If you’re anything like me, you’ve been watching the increasing growth of container-based solutions with considerable interest, and you’ve probably been experimenting with a couple of ideas. At some point in the future, perhaps you’d like to take those experiments and actually put them out there for people to use. Why wait? It’s a new year, and there is no time like the present to take some action on that goal.
Experimenting is great, and you learn a great deal, but often in the midst of trying out new things, hacking different technologies together and making it all work, things get introduced into our code which probably shouldn’t be put into a production environment. Sometimes, having a checklist to follow when we’re excited and nervous about deploying new applications out into the wild can help ensure that we don’t do things we shouldn’t. Consider this article as the start of a checklist to ready your Docker applications for prime time. Read more