Join Windows worker nodes¶
MKE allows you to add or remove nodes from your cluster as your needs change over time.
Because MKE leverages the clustering functionality provided by Mirantis Container Runtime (MCR), you use the docker swarm join command to add more nodes to your cluster. When you join a new node, MCR services start running on the node automatically.
Windows nodes limitations¶
The following features are not yet supported using Windows Server:
Encrypted networks are not supported. If you have upgraded from a
previous version of MKE, you will need to recreate an unencrypted
version of the
On Windows, Docker cannot listen on a Unix socket. Use TCP or a named pipe instead.
Configure the Docker daemon for Windows nodes¶
If the cluster is deployed in a site that is offline, sideload MKE images onto the Windows Server nodes. For more information, refer to Install MKE offline.
On a manager node, list the images that are required on Windows nodes:
docker container run --rm -v /var/run/docker.sock:/var/run/docker.sock mirantis/ucp:3.5.6 images --list --enable-windows
Pull the required images. For example:
docker image pull mirantis/ucp-agent-win:3.5.6 docker image pull mirantis/ucp-dsinfo-win:3.5.6
Join Windows nodes to the cluster¶
Log in to the MKE web UI as an administrator.
In the left-side navigation panel, navigate to Shared Resources > Nodes.
Click Add Node.
Select Windows for the node type.
Optional. Select Use a custom listen address to specify the address and port where the new node listens for inbound cluster management traffic.
Optional. Select Use a custom advertise address to specify the IP address that is advertised to all members of the cluster for API access.
Copy the displayed command, which looks similar to the following:
docker swarm join --token <token> <mke-worker-ip>
Alternatively, you can use the command line to obtain the join token. Using your MKE client bundle, run:
docker swarm join-token worker
docker swarm joincommand captured in the previous step on each instance of Windows Server that will be a worker node.