Shulou(Shulou.com)06/01 Report--

Introduction

Kubernetes (hereinafter referred to as K8s) is an orchestration engine supported by the Rancher platform. Rancher K8s has the characteristics of flexible deployment and easy to use, and Rancher is basically a synchronous update of new versions and new components that support K8s. Users can also choose to deploy the specified K8s version. However, it is difficult for us to deeply experience these conveniences in China, and the Rancher platform serving global developers cannot be individually customized for Chinese users, so I would like to share with you how to optimize the experience of Rancher K8s in China.

Key points of deployment

In the selection of operating system before deployment, relatively speaking, I recommend the combination of ubuntu+docker. After all, this combination is used by more users abroad, and the speed of bug fix is relatively fast. If you are a heavy user of docker, you should know that docker itself has a lot of bug.

If you are deploying a new Rancher environment, I recommend starting it with the following script. By setting DEFAULT_CATTLE_CATALOG_URL, you can directly specify the Rancher K8s that I have customized:

Of course, if it is a deployed Rancher environment, you need to make some simple modifications on Rancher UI. The existing library catalog repo of Disable can point to the one I have customized. Pay attention to the setting of branch. If the network condition is not good, you need to wait patiently to pull the repo content again:

Before deploying agent nodes, it is best to have a clean environment, but if you have done agent nodes before, especially those who have previously deployed rancher k8s, I strongly recommend that you perform a thorough cleaning, otherwise all kinds of unexpected situations will occur. Please refer to my script for thorough cleaning and read what you have done:

Everything OpenSource

If you have doubts about my changes in it, you can rest assured. I mainly change two places: fork rancher-catalog established a branch of k8s-cn, as long as the library catalog repo of Rancher points to my engineering branch; fork kubernetes-package, every time Rancher K8s releases a new version, I will build a CN branch based on that version (such as: v1.5.1-rancher1-7-cn), all optimization changes for China will be on this branch. Eventually, I will update the usage image in China and push it to the image repository, which is currently used by Aliyun's image repository (the signboard will not fall down in a short time.)

Reference link:

Https://github.com/niusmallnan/rancher-catalog

Https://github.com/niusmallnan/kubernetes-package

Follow-up support plan

The rancher-k8s v1.5.1-rancher1-7 version is supported at the time of this writing, and the author has tested it on Rancher v1.3.1. Following the official release of the new version of Rancher, the article will be updated synchronously and continue to do some simple tests. Consider adding offline installation in the future. You can specify a local image repository and rely on convenient features such as one-click import of images.

If you find all kinds of problems in use, the author's email niusmallnan@gmail.com is open to you, and you can always find the author in the Rancher China Wechat technology exchange group, as well as a group of partners who love Docker and open source.

Original source: Rancher Labs

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.