One of the hallmark features of Rancher 2.0 is its ability to consume Kubernetes clusters from anywhere. In this post, I’m going to walk you through using the popular kops tool to create and manage Kubernetes clusters on AWS and then bring them under Rancher 2.0 management. This walkthrough will help you create a non-HA Kubernetes cluster, though kops does support HA configurations. With this new cluster, we will run the Rancher 2.0 tech preview in a pod with a persistent volume claim. Read more
In my prior posts, I’ve written about how to ensure a highly resilient workloads using Docker, Rancher, and various open source tools. For this post, I will build on this prior knowledge, and to setup an AWS infrastructure for Rancher with some commonly used tools. If you check out the repository here, you should be able to follow along and setup the same infrastructure.
The final output of our AWS infrastructure will look like the following picture:
In less than a week, over 24,000 developers, sysadmins, and engineers will arrive in Las Vegas to attend AWS re:Invent (Nov. 28 – Dec 2). If you’re headed to the conference, we look forward to seeing you there! We’ll be onsite previewing enhancements included in our upcoming Rancher v1.2 release:
Support for the latest versions of Kubernetes and Docker: As we’ve previously mentioned, we’re committed to supporting multiple container orchestration frameworks, and we’re eager to show off our latest support for Docker Native Orchestration and Kubernetes.
Better load balancing for AWS: We recently completed additional work on the external load balancer for AWS, which is also available via Rancher catalog.
An update to our storage and networking services: While we’ve covered some changes to how we handle container networking and storage in our prior meetups, we’ve built more improvements to show off since then.
Come say hello and check out the newest features! The Rancher team will be at booth #110, with great swag and prizes, and we’re always excited to meet our users and community in person.
Not attending AWS re:Invent? Stay up-to-date with Rancher and with our upcoming release by following us on Twitter @Rancher_Labs.
Rancher ships with two types of catalog items to deploy applications; Rancher certified catalog and community catalog, which enable the community to contribute to the reusable pre-built application stack templates.
One of the recent interesting community catalog templates is the external load balancer for AWS Classic Elastic Load Balancer, which keeps an existing Load balancer updated with the EC2 instances on which Rancher services that have one or more exposed ports and specific label.
This blog post will explain how to set up a Classic ELB and walk through the details of launching a catalog template for ELB from the community catalog to update the Classic ELB automatically. Read more
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. But like Jevons’ Paradox, the more efficient we become in consuming a resource, the more of that resource we consume. So we always are seeking the newest, fastest and uber-optimized of everything.
How it works:
Spotinst is a SaaS platform that enables reliable, highly available use of AWS Spot Instances and Google Preemptible VMs with typical savings of 70-90%.
We’ve worked with the team at Spotinst to integrate with the Rancher API directly. The integration utlizes Docker “checkpoint and resume” (CRIU project). Based on metrics and business rules provided by Spotinst, Rancher can freeze any container and resume it on any other instance, automating the process a typical DevOps team might implement to manage container deployment. Read more
Hello, I’m Alena Prokharchyk, one of the developers here at Rancher. In my previous blog posts, I’ve covered various aspects of Service Discovery, a feature we use to discover and interconnect services of user applications deployed in Rancher. This discovery is done by services registering themselves dynamically to Rancher’s internal DNS so that other services in the system can discover them by fully qualified domain name (FQDN). Service Discovery can also be registered to Rancher’s Load Balancer (LB) service which allows it to balance traffic between all of a services’ containers.
Even though this covers many use cases, one major piece was lacking – making applications discoverable to outside world applications (or users) that don’t have access to Rancher’s internal DNS. I’m excited to let you know we’ve implemented a new solution that integrates our DNS service with Amazon Route53, which is now available as of Rancher 0.44. In this post I’ll describe its setup and implementation details.