Shulou(Shulou.com)05/31 Report--

This article is about the difference between Rancher 1. 6 and 2. 0. The editor thinks it is very practical, so share it with you as a reference and follow the editor to have a look.

Rancher 2.0 Beta has been officially released. Rancher 2.0 is an enterprise Kubernetes platform, which can realize the unified management of multiple Kubernetes clusters and solve the different infrastructure dilemmas that enterprise users may face in the production environment. In addition, the simple and intuitive interface style and operating experience of Rancher 2.0 will solve the long-standing problems of poor ease of use and steep learning curve of Kubernetes native UI. Coupled with a series of expanded functions such as monitoring, logging and CI/CD brought by Rancher 2.0, it can be said that Rancher 2.0 provides a more convenient way for enterprises to land Kubernetes in the production environment.

Now that the development of Rancher 2.0 is coming to an end, the Rancher Labs R & D team will focus on testing and documentation. We think it is useful to provide Rancher users with a glossary of terms at this time, which helps Rancher users understand the basic concepts of Kubernetes and Rancher.

From Rancher 1. 6 to Rancher 2. 0, Rancher products now follow more of the Kubernetes naming standard. This shift may be a little disturbing for users who used to use only Cattle environments in Rancher 1.6.

But it doesn't matter, this article will help you understand the new concepts in Rancher 2.0. It can also serve as a brief reference to terms and concepts between the container orchestration framework Cattle and Kubernetes.

Rancher 1.6Cattle and Rancher 2.0K8s comparison

The orchestration tool Cattle provided by Rancher 1.6has been favored by many users. In Cattle, you have an environment that is the boundary between management and computing, that is, the lowest level of permissions you can specify; importantly, all hosts in this environment are dedicated to this environment. Then, in order to organize your containers, you need to have a Stack, which is a logical grouping of service collections and a service as a specific running mirror.

So what does this structure look like in 2.0?

If you've been focused on the container domain, you can't miss hearing some of the terms of Kubernetes, such as pods, namespaces, and nodes. This article will compare and unify the common terms of two different container orchestration tools, Cattle and Kubernetes, to simplify the transition of Rancher users from Cattle to Kubernetes. With the change of some names, some functions have changed.

The following table gives some definitions of core Kubernetes concepts.

For more details on the concept of Kubernete, please refer to:

Https://kubernetes.io/docs/concepts/

Environment

The environment in Rancher 1.6 represents two things:

Calculation boundary

Management boundary

In 2.0, the concept of environment no longer exists and is replaced by:

Cluster (Cluster)-Computing boundaries

Project (Project)-manage boundaries

The project is the management introduced by Rancher in order to reduce the management burden of Kubernetes.

Mainframe

In Cattle, a host belongs to only one environment. Now the same is true in Rancher 2.0, where a node (the new name of the host) belongs to only one cluster. The environment that used to be made up of hosts is now a cluster of nodes.

Stack

The stack in Rancher 1.6is a way to group multiple services. In Rancher 2.0, this is done by namespaces.

Service

In Rancher 1.6, a service is defined as running one or more instances of the same container. In Rancher 2.0, one or more instances running the same container are defined as workloads, where the workload can consist of pod with controllers.

Container

A container image is a lightweight, stand-alone, executable package that contains everything you need to run it: code, runtime, system tools, system libraries, settings, and so on. Under Kubernetes, pod is the smallest unit. Pod can be a single mirror or multiple mirrors that share the same storage / network, and a description of how these mirrors interact. The content of Pod is always co-located and co-scheduled, and runs in a shared context.

Load balancer

In Rancher 1.6, the load balancer is used to expose your application from the Rancher environment, allowing external access. The concept is the same in Rancehr 2.0. There is an option for load balancer to help expose your service. In the Kubernetes language, this feature is often referred to as Ingress. In short, load balancers and Ingress play the same role.

Conclusion

Conceptually, Cattle is the closest of all orchestration tools to Kubernetes. It is hoped that this article will provide a simple reference for users who transition from Rancher 1.6 to Rancher 2.0. In addition, the similarity between Cattle and Kubernetes can also help users make better transformations.

The following table gives a quick reference for the comparison of new and old terms:

Thank you for reading! This is the end of the article on "what's the difference between Rancher 1.6and 2.0". I hope the above content can be helpful to you, so that you can learn more knowledge. if you think the article is good, you can share it for more people to see!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.