Continental Innovates with Rancher and Kubernetes
Rancher is the first multi-cluster, multi-cloud Kubernetes management platform.
Rancher 2.0 is out and odds are, you’re wondering what’s so shiny and new about it. Well, here’s a huge selling point for the next big Rancher release; Kubernetes cluster adoption! That’s right, we here at Rancher wanted more kids, so we decided it was time to adopt. In all seriousness though, this feature helps make Rancher more relevant to developers who already have Kubernetes clusters deployed and are looking for a new way to manage them.
Google Container Engine, or GKE for short (the K stands for Kubernetes), is Google’s offering in the space of Kubernetes runtime deployments. When used in conjunction with a couple of other components from the Google Cloud Platform, GKE provides a one-stop shop for creating your own Kubernetes environment, on which you can deploy all of the containers and pods that you wish without having to worry about managing Kubernetes masters and capacity.
Update: Rancher 2.0 Tech Preview has since gone to GA. Read the announcement here.
-- We achieved another significant milestone today at Rancher Labs. After months of hard work, our engineering team released a technology preview of the Rancher 2.0 container management platform.] Rancher 2.0 builds on the tremendous momentum of market-leading Rancher 1.x container management software. Since we shipped Rancher 1.0 in March 2016, Rancher server and Rancher agent have been downloaded over 60 million times.
This latest release makes it possible to manage all Kubernetes clusters under a single Rancher instance.
I’m pleased to announce that Rancher has released a new Terraform module for deploying Rancher on Google Compute Engine (GCE). This complements our existing module for Amazon Web Services (AWS). Terraform is an excellent tool for managing infrastructure as code, and many of our users already make use of it elsewhere in their environments. Using this module along with either GCE or AWS to orchestrate Rancher gives you the ability to define the entirety of the stack—from the application layer being managed by Docker Compose or Kubernetes resource YML in Rancher all the way down to the servers and networks in the Terraform plan.
](https://cdn.rancher.com/wp-content/uploads/2015/11/16025649/spotinstlogo.png) We are very excited to announce a new partnership with Spotinst today to deliver intelligent management and migration of container workloads running on spot instances. With this new solution, we have developed a simple, intuitive way for using spot instances to run any container workload reliably and for a fraction of the cost of traditional applications. Since the dawn of data centers we’ve seen continuous improvements in utilization and cost efficiency.
Recently Rancher provided a disk image to be used to deploy RancherOS v0.3 on Google Compute Engine (GCE). The image supports RancherOS cloud config functionality. Additionally, it merges the SSH keys from the project, instance and cloud-config and adds them to the rancher user.
Building The Setup In this post, I will cover how to use the RancherOS image on GCE to set up a MongoDB Replica Set. Additionally I will cover how to use one of the recent features of Rancher platform which is the Load Balancer.
As you may have seen, Rancher recently announced our integration with docker-machine. This integration will allow users to spin up Rancher compute nodes across multiple cloud providers right from the Rancher UI. In our initial release, we supported Digital Ocean. Amazon EC2 is soon to follow and we’ll continue to add more cloud providers as interest dictates. We believe this feature will really help the Zero-to-Docker _(and Zero-to-Rancher)_ experience. But the feature itself is not the focus of this post.
Hi everyone, I recorded a brief overview of how to launch a Rancher 0.3 environment, connect it with some resources from a few different public clouds, and then deploy an application. If you’d like to learn more about Rancher, please visit our GitHubsite for information on joining the community, or downloading the software. You can also schedule a demo to talk with one of our engineers about the project.
In my current role at Rancher Labs, we do a lot of testing and provisioning on Google Compute Engine. One of the things that we found missing were official Ubuntu and Fedora images. Fortunately, Ubuntu now has official images on GCE and we hope that Fedora follows as well. There is an open issue to track the official progress, but in the meantime the new Fedora 21 cloud image is straight forward enough to get going.