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

When we released Rancher v1.2 in early December 2016, we made plans for "more frequent iterations" in the future. Just last week, Rancher v1.3 was officially released! In addition to some bug fixes in v1.2, it has several new features: 1) user interface fixes; 2) changes to the DNS engine; and 3) improvements to Kubernetes and related tools.

Most importantly, in Rancher v1.3, we began to address a frequent request from users: support for Windows 2016!

The support for Windows in Rancher v1.3 is still experimental and limited, but it is an important step for Rancher Labs to serve the needs of its customers. Containers are more and more widely used in enterprises, while worldwide, a large part of the workload is running on Windows servers and client systems. And that will not change in the foreseeable future.

The goal of Rancher Labs is to make applications truly portable between the cloud and infrastructure, and having workloads running on top of Windows containers is a key part of Rancher Labs's vision.

Windows in Rancher tutorial

To deploy Windows in Rancher, you first need to create a new environment where the container orchestration needs to be set to Windows in the environment template.

Currently, Rancher only supports the creation of containers on specific hosts. Some features that may appear in Cattle in UI, such as service discovery, health check, metadata, DNS, and load balancer, are not supported at this stage.

Note: Rancher has provided you with a default Windows environment template available. But if you create your own Windows environment template, you need to disable all other infrastructure services because they are currently incompatible with Windows.

Create a Windows environment

In the environment drop-down list, click Manage Environment (manage Environment). To create a new environment, click Add Environment, provide a name, description (optional), and then select the environment template with Windows as the orchestration. If you turn on access control, you can add members here and select their member roles. Anyone in the member list can access your environment.

After creating the Windows environment, you need to navigate to the environment, where you can select the name of the environment from the drop-down menu located in the upper left corner, or select "Switch to this Environment" from the specific environment drop-down menu.

Note: Rancher supports multiple container orchestration frameworks, but at this stage, users cannot switch environments if services are already running in some environments.

Add Windows host

To add a host to Windows, you need to first install a host running Windows Server 2016 with Docker.

In the Infrastructure tab, you will get a custom command to start the Rancher agent service. You can follow the instructions to start the Rancher proxy service in Windows.

On the host, the agent binaries will be downloaded to a folder called C:/Program Files/rancher, and the agent logs will be located in C:/ProgramData/rancher/agent.log.

Delete Windows host

When you add a host to Rancher, the Rancher agent is part of it, and it is installed and registered on the host as a service. In order to reuse the host, you must delete the existing service. You can run the following command in powershell. After removing the service, you can re-use the host in the Windows environment.

&'C:\ Program Files\ rancher\ agent.exe'-unregister-service

Network in Windows

By default, we support NAT and transparent networks.

Currently, the default Windows environment template supports a transparent network called transparent, which is created by running docker network create-d transparent transparent.

If you want to create a transparent network with a different name, you need to use Windows to create a new environment template as a container orchestration. After selecting Windows, you can click "Edit Config" to change the name of the transparent network. The default name is transparent. After you create an updated environment template, you can create a new environment to support the newly named

Transparent network. UI will continue to use transparent as the default name, so you need to update this command to docker network create-d transparent

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.