Continental Innovates with Rancher and Kubernetes
This demonstration by Rancher Engineer Prachi Damle shows users how to migrate applications from Rancher 1.6 Cattle to Rancher 2.0 Kubernetes.
Although more and more companies choose to containerize their applications and to use Kubernetes to orchestrate their containers, they continue to face a common challenge: how to preserve application data even after a container closes. Without the ability to persist data, containers might seem to have limited use in many workloads, especially in stateful applications and database architectures. Fortunately many solutions exist.
Join Rancher Labs as we do a deep dive into storage solutions for Docker containers and Kubernetes and discuss best practices for a wide variety of storage use cases.
This article is a continuation in a series on migrating from Rancher 1.6 to Rancher 2.0. Learn more about application load balancing options in Rancher 2.0
Rancher 1.6 is a widely used container orchestration platform that runs and manages Docker and Kubernetes in production. This article is a continuation in a series on migrating from Rancher 1.6 to Rancher 2.0. This article explores how to map the 1.6 scheduling options to Rancher 2.0
When your application is user-facing, ensuring continuous availability and minimal downtime is a challenge. Hence, monitoring health of the application is essential to avoid any outages. This article explains how to monitor the health of your applications on Kubernetes clusters in Rancher 2.0.
This article is a continuation in a series on migrating from Rancher 1.6 to Rancher 2.0. It explores how to expose Kubernetes workloads publicly using port mapping in Rancher 2.0
Rancher 1.6 is a widely used container orchestration platform that runs and manages Docker and Kubernetes in production. This article is a continuation in a series on migrating from Rancher 1.6 to Rancher 2.0
This blog covers building a CI/CD Pipeline using the hosted GitLab.com solution. The Kubernetes integrations that are covered are generic and should work with any CI/CD provider that interface directly to Kubernetes using a service account. Tools used are Auto Devops, Rancher, and Gitlab.
In this blog series, we will try to explore how various features supported by Rancher 1.6 using Cattle can be mapped to their equivalents in the Kubernetes world using Rancher 2.0. Read part 1 here.
Service mesh is a new technology stack aimed at solving the connectivity problem between cloud native applications. Read an overview at the Rancher blog.
We are excited to announce a new version of rancher released on July 11th, 2018. The latest release is version 2.0.6. Read an overview of the new enhancements and new features in Rancher, open-source container management for running apps in production.
Learn about Rancher management plane architecture where every API resource is represented as a CustomResourceDefinition(CRD) and every functional routine runs as Kubernetes controller
Some of the cool new features that have been introduced in Rancher 2.0 include Alerting. These Kubernetes monitoring features were frequently asked for under 1.x so were high on the feature list for when we started development on 2.0. Learn how to create Kubernetes cluster-level and workload alerts in Rancher 2.0.
Don't have access to Cloud infrastructure? Maybe you would like to use Rancher for local Kubernetes deployments just like you do in production? No problem, you can install Rancher 2.0 on your desktop. Learn how here.
It’s sometimes not possible to use hosted services like GKE or AKS, and there are occasions where direct internet access is not possibe (offline/airgapped). In these instances it is still possible to use Rancher to manage your clusters.
In this post we’ll walk through what you need to do when you want to run Rancher 2.0 in an offline/air gapped environment.
Docker Private Registry Everything Rancher related runs in a container, so a place to store the containers in your environment is the first requirement.
Rancher 2.0 is an open-source, enterprise Kubernetes container orchestration platform for running containers in production.
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.
Rancher 2.0 was built with many things in mind. You can provision and manage Kubernetes clusters, deploy user services onto them and easily control access with authentication and RBAC. One of the coolest things about Rancher 2.0 is its intuitive UI, which we’ve designed to try and demystify Kubernetes, and accelerate adoption for anyone new to it. In this tutorial I’ll walk you through that new user interface, and explain how you can use it to deploy a simple NGINX service.
Today we released the second tech preview of Rancher 2.0, our next major Rancher product release. We’ve been hard at work since the last tech preview release in September 2017, driven by the overwhelmingly positive response to our Rancher 2.0 vision and a great deal of feedback we have received.
The Tech Preview 2 release contains many significant changes and enhancements:
Rancher server is now 100% written in Go and no longer requires a MySQL database.
We’re about to start the Rancher 2.0 beta program, so for this month’s meetup we’ll be providing a detailed look at the latest release of Rancher, and explaining how to get involved with the Beta. Rancher 2.0 is designed to make all aspects of leveraging Kubernetes easier for both users and admins, and we’ll highlight many of the latest features in this online meetup.
During the meetup we’ll be demoing the new release including all of the user-level features.