- b and c: There are two labels that are always required. We will need to ensure Interlock forwards the service's requests using com.docker.lb.hosts and com.docker.lb.port. These will have all the required information, but com.docker.lb.network is recommended and required if the service's instances are attached to more than one network. We need to specify which network should be used as an ingress.
- b: The Interlock solution is based on a main process named interlock, a process for managing external proxy services and configurations, and an interlock-proxy service that will run inside the Docker Enterprise environment if no external load balancer is specified. These three processes run as services within Docker Swarm and they are prefixed with ucp-. ucp-interlock-controller does not exist.
- d: By default, only the ucp-interlock service will be located by the node's roles. All other components can run anywhere. We will use location constraints to run the ucp-interlock...
United States
United Kingdom
India
Germany
France
Canada
Russia
Spain
Brazil
Australia
Argentina
Austria
Belgium
Bulgaria
Chile
Colombia
Cyprus
Czechia
Denmark
Ecuador
Egypt
Estonia
Finland
Greece
Hungary
Indonesia
Ireland
Italy
Japan
Latvia
Lithuania
Luxembourg
Malaysia
Malta
Mexico
Netherlands
New Zealand
Norway
Philippines
Poland
Portugal
Romania
Singapore
Slovakia
Slovenia
South Africa
South Korea
Sweden
Switzerland
Taiwan
Thailand
Turkey
Ukraine