Docker Universal Control Plane can be installed on-premises, or on a virtual private cloud. If you’ve never used Docker UCP before, you should start by installing it on a sandbox.
This article explains what you need to consider before deploying Docker Universal Control Plane.
Before installing UCP, you should make sure all nodes of your cluster comply with the system requirements.
Docker UCP requires the Docker CS Engine to run. Before installing Docker CS Engine on the cluster nodes, you should plan for a common naming strategy.
Decide if you want to use short hostnames like
engine01 or Fully Qualified
Domain Names (FQDN) likes
engine01.docker.vm. Independently of your choice,
ensure your naming strategy is consistent across the cluster, since UCP uses
As an example, if your cluster has 4 hosts you can name them:
engine01.docker.vm engine02.docker.vm engine03.docker.vm engine04.docker.vm
Docker UCP requires each node on the cluster to have a static IP address. Before installing UCP, ensure your network and nodes are configured to support this.
In distributed systems such as Docker UCP, time synchronization is critical to ensure proper operation. As a best practice to ensure consistency between then engines in a UCP cluster, all engines should regularly synchronize time with a NTP server. If a server’s clock is skewed, unexpected behavior may cause poor performance or even failures.
UCP Docker UCP does not include a load-balancer. You can configure your own load-balancer to balance user requests across all controller nodes.
If you plan on using a load balancer, you need to decide whether you are going to add the nodes to the load balancer using their IP address, or their FQDN. Independently of what you choose, it should be consistent across the nodes.
After that, you should take note of all IPs or FQDNs before starting the installation.
By default, both UCP and DTR use port 443. If you plan on deploying UCP and DTR, your load balancer needs to distinguish traffic between the two by IP address or port number.
You can customize UCP to use certificates signed by an external Certificate Authority. If you decide to use your own CAs take in consideration that:
You can have a certificate for each controller, with a common SAN. As an example, on a three node cluster you can have:
Make sure you can transfer file between the hosts on the cluster. You will need to replicate CAs across controller nodes.
For this, you can tools like
rsync, or configure the hosts to use
a network file system.
Пожалуйста, авторизуйтесь что бы оставлять комментарии.