Incompatibilities and breaking changes预计阅读时间: 1 分钟
This is the list of incompatibilities introduced by Universal Control Plane 2.1.
HTTP routing mesh
When using the HTTP routing mesh you need to apply specific labels to your services to make them accessible using a hostname. The syntax used for these labels has changed on 2.1.
If you were using this feature on UCP 2.0, after you upgrade you’ll have to
update your services to use a new label syntax.
You can do this from the UCP web UI or from the CLI using the
docker service update command.
There are two changes to consider.
First, a route was previously in the format of
external_route. Now the format is a comma separated list of
Second, if you have multiple routes to the same service, these were previously
written as a comma separated list of the above. These are now separate labels,
one per route, prefixed with
Below you can find examples on how to upgrade from the old syntax to the new one.
A single route with a single internal port
Old syntax http://example.com New syntax external_route=http://example.com How to upgrade docker service update \ --label-add com.docker.ucp.mesh.http=http://example.com \ <service-name>
A single route with an explicit internal port
Old syntax 8080=http://example.com New syntax external_route=http://example.com,internal_port=8080 How to upgrade docker service update \ --label-add com.docker.ucp.mesh.http=external_route=http://example.com,internal_port=8080 \ <service-name>
Two routes, each to a different internal port
Old syntax 8080=http://foo.example.com,1234=http://bar.example.com New syntax external_route=http://foo.example.com,internal_port=8080 external_route=http://bar.example.com,internal_port=1234 How to upgrade docker service update \ --label-remove com.docker.ucp.mesh.http \ --label-add com.docker.ucp.mesh.http.foo=external_route=http://foo.example.com,internal_port=8080 \ --label-add com.docker.ucp.mesh.http.bar=external_route=http://bar.example.com,internal_port=1234 \ <service-name>