Illumina Innovates with Rancher and Kubernetes
In any rapidly emerging market, consultants can be a great source for vendor-neutral insights, as they typically work with multiple technologies to help their customers make informed decisions. In that vein, Derya (Dorian) Sezen of kloia, a new-era consulting organization that provides services toward transition of legacy workloads to frontline technologies in Cloud, DevOps and Microservices, recently wrote a blog summarizing his experience with Rancher and Red Hat OpenShift. In his blog, Dorian compared and scored the two Kubernetes management tools across 13 categories including installation easiness, CNCF/industry standards, open-source, licensing, multi-cluster, upgrades, Kubernetes version, vendor-lock, Windows container support, support, sales, partner ecosystem and bundle options.
Introduction With the rise of the containerization technology and increased attention from enterprises and technologists in general, more and more containerized applications have been deployed to the cloud. Moreover, research conducted by 451 Research predicts that the application container market will grow dramatically through 2020, which will continue to expand the number of containerized applications in the cloud.
When the scale and complexity of production-critical containers rises, container orchestration tools step into the picture and fill an important gap in the container management toolbox.
Introduction Ready to make the big move to containers? If you’re thinking of moving services from an existing, non-containerized system to a container-based environment, you’re probably wondering how to do it.
Is there a right way? Is there a best way? Is there an easy way to lift-and-shift existing components that can be applied to all applications? The answer to those questions is — in general, yes.
While the specifics of a migration to containers and microservices will vary from organization to organization, there are general principles and best practices that you should follow to achieve a seamless transition of your apps from legacy infrastructure to a containerized environment.
Introduction Servers are expensive. And in single-application installations, most servers spend the majority of their time waiting. An attempt to make the most of these expensive assets led to the development of virtualization. In turn, making the most of virtualization has led to multiple options for virtualizing applications.
Hardware virtualization, like VMware, and process virtualization through containers, like Docker, offer competing methods for virtualizing applications. Both technologies work to make the most of limited hardware resources, but they do so in significantly different ways.
This article will compare and contrast six operating systems commonly used in container deployments. It will present information on why the choice of operating system matters, and how differences in application may require differences in operating system.
In this article, we talk about monitoring for scaling and life cycle management with the help of built-in tools like probes and horizontal pod autoscaler. A previous article covered monitoring and metrics for users using tools like the Kubernetes dashboard and cAdvisor. We will test each one of these tools to see what they offer and how they can help us.
In this article, we talk about monitoring Kubernetes with the help of built-in tools like the dashboard and cAdvisor. In part 2, we will cover scaling and life cycle management using other built-in tools like probes and horizontal pod autoscaler. We will then test each one of these to see what they offer and how they can help us.
CNI, or container network interface, is a standard system for provision networking for containers, especially for multi-host orchestrators like Kubernetes. In this article, we'll describe what CNI is, why it's helpful, and then compare some popular CNI plugins for establishing the network for Kubernetes containers.
A brief look into the critical differences of VMware vs Docker containers as a platform for application deployment.
Microservices are an alternative to monolithic application architecture that can help businesses adapt to modern deployment environments and increase their development velocity. In this article, we'll discuss the differences between these two approaches and the reasons organizations might want to consider microservices.
This article covers some of the major advantages and disadvantages of two of the most popular container orchestration tools: Kubernetes and Docker Swarm. We describe each piece of software and then dive in to compare across different features.
Kubernetes vs Docker: What's the difference? Read our introduction to Docker and Kubernetes, and the pressures of delivering reliable applications at scale.
Rancher 1.6 and Rancher 2.0 have slightly different terms and concepts underpinning the container orchestration engine. Learn the fundamental differences between Cattle and Kubernetes. For anyone who has used Cattle or is new to Kubernetes, this article is for you. Get a container orchestrator Cattle to Kubernetes glossary cheatsheet as well.
Introduction Jenkins has been the industry standard CI tool for years. It contains a multitude of functionalities, with almost 1,000 plugins in its ecosystem, this can be daunting to some who appreciate simplicity. Jenkins also came up in a world before containers, though it does fit nicely into the environment. This means that there is not a particular focus on the things that make containers great, though with the inclusion of Blue Ocean and pipelines, that is rapidly changing.
Container monitoring environments come in all shapes and sizes. Some are open source while others are commercial. Some are available in the Rancher Catalog while others require manual configuration. Some are general purpose while others are aimed specifically at container environments. Some are hosted in the cloud while others require installation on own cluster hosts.
In this post, we take an updated look at 10 container monitoring solutions. This effort builds on earlier work including Ismail Usman’s Comparing 7 Monitoring Options for Docker from 2015 and The Great Container Monitoring Bake Off Meetup in October of 2016.
Rancher looks at what you need to know about serverless computing, how it compares to containers, and how it can figure into your IT strategy. Learn more.
For teams building and deploying containerized applications using Docker, selecting the right orchestration engine can be a challenge. The decision affects not only deployment and management, but how applications are architected as well. DevOps teams need to think about details like how data is persisted, how containerized services communicate with one another, load balancing, service discovery, packaging and more. It turns out that the choice of orchestration engine is critical to all these areas.
Note: You can find an updated comparison of Kubernetes vs. Docker Swarm in a recent blog post here.
Recent versions of Rancher have added support for several common orchestration engines in addition to the standard Cattle. The three newly supported engines, Swarm (soon to be Docker Native Orchestration), Kubernetes and Mesos are the most widely used orchestration systems in the Docker community and provide a gradient of usability versus feature sets.
*Note: Since publishing this post, we’ve created a guide comparing Kubernetes with Docker Swarm. You can read the details in the blog post here..* Over the last six months, Rancher has grown very quickly, and now includes support for multiple orchestration frameworks in addition to Cattle, Rancher’s native orchestrator. The first framework to arrive was Kubernetes, and not long after, Docker Swarm was added. This week, the team at Rancher added support for Mesos.