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

This article mainly introduces the function of Rancher 2.4.3 Stable, which is very detailed and has certain reference value. Friends who are interested must finish it!

Rancher 2.4 was officially released on April 1, 2020, which is a very important milestone version of Rancher 2.x. The new features of Rancher 2.4 include the scalability of edge computing deployment scenarios, zero downtime upgrade clusters, enhanced security, and new hosting options to provide users with an one-stop management experience for massive Kubernetes clusters from data center to cloud to edge.

Since the release of Rancher 2.0 in 2018, Rancher has been working to simplify Kubernetes and accelerate enterprise innovation in hybrid cloud scenarios. Based on this, Rancher has created the industry's first hybrid cloud Kubernetes management platform, and has become the only multi-cloud and multi-cluster Kubernetes management platform in the industry that can meet enterprise heterogeneous infrastructure. The official release of Rancher 2.4 further provides enterprises with the operational efficiency, scalability, and security needed to run Kubernetes on any infrastructure.

The release of Rancher 2.4 has been followed and supported by a large number of Rancher users, and almost every day people ask: when will Rancher 2.4 release the stable version? In the past month, the R & D and testing team of Rancher has conducted a large number of tests and optimizations on the performance, stability and security of Rancher 2.4, and added some new features to the original foundation. Today, Rancher officially released Rancher 2.4.3 and added support for EKS hosting services in China in this version. This is the first stable version of Rancher 2.4.x and a stable version that Rancher officially recommends for all users in production environments.

Important features of Rancher version 2.4

Rancher 2.4 Rancher provides the scalability, administrative capabilities, and security capabilities needed to support Kubernetes in very large-scale edge scenarios. Key enhancements to Rancher 2.4 include:

Massive cluster management: Rancher 2.4 GA version supports 2000 clusters and 100000 nodes. What's more, the product architecture of Rancher 2.4 has been enhanced to provide a way to support 1 million clusters in the upcoming release.

Excellent choice when network conditions are limited: for clusters without fixed or stable network connections, the combination of Rancher 2.4 + K3s is the best choice to manage, upgrade and repair clusters. Rancher 2.4 can start the upgrade remotely, but the upgrade process will be managed on the local K3s cluster, allowing users to manage the upgrade and repair the cluster locally, and then synchronize with the management server after the network connection is restored

RKE supports zero downtime upgrade clusters: as more and more organizations use Kubernetes to run applications that host enterprise critical business in production environments, they have a growing desire to maintain their Kubernetes infrastructure in an uninterrupted manner. Rancher 2.4 supports zero downtime upgrade clusters, which allows organizations to upgrade Kubernetes clusters and nodes without interrupting applications. In addition, users can select and configure their add-ins and upgrade strategies so that DNS and Ingress are not affected by service outages

Enhanced security through CIS benchmark scanning: cluster security is critical to a successful Kubernetes strategy. However, according to the latest research from AimPoint, 44% of companies have delayed the use of containerized applications in production environments because of security concerns about Kubernetes containers. In order to help enterprises solve this problem, Rancher 2.4 creatively introduced CIS security scanning. According to more than 100 CIS security benchmarks issued by the Internet Security Center, combined with the actual definition of Kubernetes cluster security, users can conduct point-to-point (ac-hoc) security scanning of RKE clusters. Users can create custom test configurations, set notification alarms for scan completion / scan failure, and take corrective actions based on this information to ensure that these clusters meet all security requirements

Rancher managed services: many organizations may be lacking or unwilling to spend the infrastructure, computing, and human resources needed to deploy and manage local Rancher Server. In response to this user demand, since Rancher 2.4, we have provided Rancher hosting services, and each customer has access to a dedicated AWS instance of the Rancher Server management control plan. Rancher managed service is a full-featured Rancher Server that provides 99.9% SLA, as well as stress-free upgrades, security patches, and backups. Downstream clusters such as GKE and AKS are not included in SLA, but continue to be operated by the corresponding K8S distribution vendors. In terms of localization and localization operations, Rancher will also launch Rancher hosting services deployed on Aliyun for customers in China.

Rancher 2.4.3 function Optimization

Node template

Support to configure custom image name and ID in Azure node template [# 23010]

Managed cluster update

Support the creation of EKS clusters in AWS China, the two regions are cn-northwest-1 and cn-north-1 [# 25613]

Display the regional information of clusters such as AKS/GKE/EKS on the cluster dashboard page [# 25656]

Mail notification enhancement

Add alarm-related information to the notification email of alarm recovery [# 24156]

UI enhancement

Support custom Header and Footer, and configure their background colors to make it easy to distinguish the current environment [# 25694]

Operating system verification

Verified SUSE Linux Enterprise Server 15 SP1 [# 26143]

Verified SUSE Linux Enterprise Server 12 SP5 using kernel version 4.12.14-122.17 [# 26287]

Fixed important bug since 2.4.2

Fixed cattle-cluster-agent memory leak in v2.4 [# 26633] [# 26577]

Fixed a problem caused by Rancher Server memory leak in v2.4 [# 21361]

Fixed display of user names of other users instead of currently logged-in users in personal preferences in some cases [# 14420]

Fixed a very slow login to Rancher using LDAP when you have many groups in your LDAP [# 26061]

Fixed an issue where Boolean values could not be parsed correctly when using the-- values parameter in CLI [# 21083]

Fixed the problem that the Worker node deleted in UI could not be rejoined due to improper cleaning of the node (if you deleted a non-Worker node, you still need to clean it) [# 23254]

Fixed failure to create Azure node templates using AzureUSGovernmentCloud endpoints [# 23350]

Fixed an issue where the EKS cluster version could not be upgraded in Rancher after the EKS cluster was modified in the AWS console [# 24171]

Fixed an issue where projectId needs to be passed in when upgrading applications in the project-level application store through API [# 24371]

Fixed an issue where AWS API keys used by EKS clusters could not be replaced [# 25835]

Fixed an issue where Rancher Server installed on a single node of Docker could not generate a self-signed certificate after upgrading to v2.4.2 in some cases [# 26457]

Fixed an issue where you could not connect directly to RKE clusters created in 2.4.They could only connect to these clusters through Rancher [# 26555]

In some cases, a single-node K3s cluster still shows Upgrading status even after upgrading the cluster [# 26286]

Fixed an issue that started to disperse the next node during a downstream cluster upgrade while the previous node was still incomplete [# 26401]

The above is all the content of this article "what is the function of Rancher 2.4.3 Stable?" Thank you for reading! Hope to share the content to help you, more related knowledge, welcome to follow the industry information channel!

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.