Tag: community

Setting up Traefik as a Dynamically-Configured Proxy and Load-Balancer

July 12, 2017

When deploying applications in the container world, one of the less obvious points is how to make the application available to the external world, outside of the container cluster. One option is to use the host port, which basically maps one port of the host to the container port where the application is exposed. While this option is fine for local development, it is not viable in a real cluster with many applications deployed. One solution is to use an HTTP proxy/load balancer. This container will be exposed using standard HTTP/HTTPS ports on the host, and will route traffic to the application running as a container.

In this post, we will setup Traefik as an HTTP proxy / load balancer for web services running in a Rancher Cattle setup. Traefik will dynamically update its configuration using the Rancher API. An SSL wildcard cert will be used. The (nice) Let’s Encrypt ACME feature Traefik is offering will not be used here. We will make use of Rancher secret feature. If you plan to use Traefik with Let’s Encrypt SSL certs, I encourage you to use the Traefik stack available in Rancher Community Catalog.

Read more

Rancher and the Moby Project

April 21, 2017

This week, the Moby Project was introduced with the idea of componentizing Docker into a series of assemblies. At DockerCon, a neat demo was done using the moby tool to assemble various components into customized Linux operating system images. While very cool, this seemed to have confused people – we’d like to provide some more background and explanation about the Moby Project and how it affects Rancher, RancherOS, and our users.


Some background on the Moby Project

The transition to the Moby Project actually started a couple of months ago, with a discussion among the Docker Project maintainers, about the dual nature of Docker as both a product and a project. This dual nature served Docker (the project and the company) well in the beginning, but at the end of the day, Docker, Inc. must make hard decisions about what their product should and will be. As a group of maintainers, we agreed that the product and project should be split. Read more

Rancher Events in December

December 6, 2016

rancher-logo_stacked-full-colorWe’re winding down for the year, but you’ll still be able to check out Rancher in a few places, live and in real-time. We always look forward to meeting users whenever we can, and hearing from you only helps make us better.


Meetups and Talks

Dec 3, Montreal, CN: Architecting Distributed Applications Across Datacenters and Clouds. Join us as we discuss popular orchestrators, and strategies for operationalizing distributed applications across diverse infrastructure.

Dec 8, Tokyo, JPN: Rancher Meetup #2. Our second meetup in Tokyo showcases real-life use cases from local users, and a quick overview of the latest features from Rancher 1.2.

Dec 8, Online: Rancher Training. A hands-on overview of how to setup a Rancher deployment (you can always check this out at rancher.com/training).

Dec 14, Online Meetup: Deep Dive on Rancher 1.2 This month, we shipped the latest version of Rancher, which brings in a massive set of improvements. See the newest support for container storage and networking, and how we wrap them into templates for container-ready environments.

Dec 20, Lyon, FR: Introduction to Rancher. Rachid Zarouali will be providing an introduction to the Rancher container management platform at the Lyon Docker meetup, along with a short overview of adjacent technologies like Prometheus and Grafana.

Don’t see anything in your area? Let us know where we can meet you.

Are you talking about Rancher in your town? Let us know @Rancher_Labs, and we’ll give you a shout out!


Rancher Events in November: Meetups, In-Person Training, and More!

November 1, 2016

rancher-logo_stacked-full-colorWe’ve been really fortunate at Rancher to have an enthusiastic community of users around the world, and we always looking forward to seeing and meeting our users in person. Here’s a few places Rancher will be in November. Please come say hi (and by the way, you can always keep track of where we’re headed at rancher.com/events)!

Don’t see anything in your area? Let us know where we can meet you.

Meetups and Talks

You can see us around the world this month, as we discuss all the challenges of managing containers in the enterprise:

Read more

How Microservices, Containers, and Open Source Contributions Have Shaped Rancher (So Far)

June 16, 2016

Rancher Labs has been developing open source projects for about two years now. We have a ton of GitHub repositories under our hood, and our number keeps growing. The number of external contributions to our projects keeps growing, too; Rancher has become more well-known over the past year, and structural changes to our code base have made it easier to contribute.

So what are these structural changes? I would highlight 3 major ones:

  1. Moving key Rancher features into separate microservices projects (Metadata, DNS, Rancher compose, etc.)
  2. Dockerizing microservices deployments
  3. Cataloging Dockerized application templates, and enabling them for deployment through the Rancher catalog

Item 2 acts as a bridge from 1 to 3. In this article, I will go over each item in more detail.

Moving key Rancher features to microservices

It is well-known that monolithic systems come with certain disadvantages:

  • Their code bases are not easy to understand and modify
  • Their features are hard to test in isolation
  • They have longer test and release cycles.

But even if your code base is pluggable and well-structured, the last two challenges note above persist. Moving code into microservices helps to overcome these challenges, and creates a lower threshold for external committers: if you are new to open source development and willing to start contributing, smaller projects are simply easier to grasp. In addition, if you look at the project pull request history for Rancher External DNS, you might see something interesting:

DNS Service Provide pull requests

The majority of commits came from people with knowledge of different service providers. From a contributor’s point of view, having and bringing in specific service provider expertise reduces the pressure associated with making initial contributions to the project. And of course, the project benefits from getting all these provider extensions.

Dockerizing microservices

Let’s say as a contributor, you’ve created this new cool DNSimple provider plug-in. It was released with an external-dns service, and now you want to try it in Rancher. To adopt the changes, you don’t have to wait for the next Rancher release, nor do you have to change the Rancher code base. All you have to do is:

  • fetch the last released image from the external-dns dockerhub repo
  • create a docker-compose template with your service’s deployment details



  •  Register your image in Rancher catalog repo (more on how to deploy it from Rancher catalog, in the next section).

Deploying the service through Rancher catalog

At Rancher, we want to provide an easy way for users to describe and deploy their Docker-based applications. The Rancher catalog makes this possible. By selecting an entry from the catalog, and answering several questions, you can launch your service through the Rancher platform.

Screen Shot 2016-06-09 at 3.23.56 PM

All the services are grouped by category, so it is easy to search for a specific functionality:

grouping by category

Pick your newly added DNSimple service, fill in the fields and hit Launch:

Screen Shot 2016-06-09 at 4.42.00 PM

That’s it! Your service gets deployed in Rancher, and can be discovered and used by any other application.

The catalog enables easy upgrades for microservices. Once the new service image is available and its template is published to the catalog, Rancher will get a notification, and your service can be upgraded to the latest version in a rolling fashion. The beauty of this is that you don’t have to update or upgrade Rancher when a new version of a microservice gets released.

Besides providing a simple way of defining, deploying and upgrading microservices, the Rancher Catalog acts as a shared template library. If you are interested building an Elasticsearch microservice, using GlusterFS, or dockerizing DroneCI, check out their corresponding catalog items. And if you want to share your application, you can submit it to our Community catalog repo.

How microservices benefit Rancher as an orchestration platform

We’ve seen the single service implementation and deployment flow; let’s look at the bigger picture now. Any container orchestration platform should be easily extendable, especially when it comes to implementing a specific service provider extension. Building and deploying this extension shouldn’t be tightly coupled to the core platform, either. Moving out the code to its own microservice repo, dockerizing the service, and allowing it to deploy it using catalog, makes everything easier to maintain and support (as pictured below):

Rancher catalog services

We are planning to move the rest of Rancher’s key services to their own microservices. This will allow users to integrate the system service plugins of their choice with just a couple of clicks.

Learning from our community

Moving our key services – Metadata, Internal DNS – into dockerized microservices written in Go has helped with the release management, and driven more external commits. We’ve taken things one step further and developed an application catalog where users can share their applications’ templates in docker-compose format. This has taught us more about best DevOps best practices from within our community, made us more familiar with their use cases, and helped us improve our microservices implementations.

Working on an open source project is always a two-way street – making your code easier to understand and manage helps the community contribute to and enhance the project. We have an awesome community, and appreciate every single contribution. We will continue improving contributors’ experience and learning from them.



Alena Prokharchyk is a principal software engineer at Rancher Labs.

If you have any questions or feedback, please contact me on twitter @lemonjet, or on GitHub (alena1108).