mirror of https://github.com/docker/docs.git
Improve release notes for UCP 2.1.0
This commit is contained in:
parent
c70a3d4636
commit
2a6ebcbd1b
|
|
@ -15,27 +15,29 @@ upgrade your installation to the latest release.
|
||||||
(9 Feb 2017)
|
(9 Feb 2017)
|
||||||
|
|
||||||
This version of UCP extends the functionality provided by CS Docker Engine
|
This version of UCP extends the functionality provided by CS Docker Engine
|
||||||
1.13.0. Before installing or upgrading this version, you need to install CS
|
1.13. Before installing or upgrading this version, you need to install CS
|
||||||
Docker Engine 1.13.1 in the nodes that you plan to manage with UCP.
|
Docker Engine 1.13 in the nodes that you plan to manage with UCP.
|
||||||
|
|
||||||
**New features**
|
**New features**
|
||||||
|
|
||||||
* Core
|
* Core
|
||||||
* You can now deploy an application stack composed of multiple services using
|
* Support for managing secrets (e.g. sensitive information such as passwords
|
||||||
a compose file v3
|
or private keys) and using them when deploying services. You can store secrets
|
||||||
* Support for managing secrets like passwords of private keys, and using them
|
securely on the cluster and configure who has access to them, all without having
|
||||||
when deploying services. You can configure who has access to configure secrets
|
to give users access to the sensitive information directly
|
||||||
and use them in their applications, without having to given them access to the
|
* Support for Compose yml 3.1 to deploy stacks of services, networks, volumes,
|
||||||
sensitive information directly
|
and secrets.
|
||||||
* Official support for routing hostnames to services. It now supports HTTPS
|
* HTTP Routing Mesh now generally available. It now supports HTTPS passthrough
|
||||||
passthrough where the TLS termination is performed by your services. It also
|
where the TLS termination is performed by your services, Service Name Indication
|
||||||
supports Service Name Indication (SNI) extension of TLS
|
(SNI) extension of TLS, multiple networks for app isolation, and Sticky Sessions
|
||||||
* Early access Windows Server support for worker nodes
|
* Granular label-based access control for secrets and volumes
|
||||||
* You can now see node metrics like disk and memory usage
|
(NOTE: unlike other resources controlled via label-based access control, a
|
||||||
* Added access control for volumes
|
volume without a label is accessible by all UCP users with Restricted Control
|
||||||
|
or higher default permissions)
|
||||||
|
|
||||||
* UI/UX
|
* UI/UX
|
||||||
* You can now view and manage application stacks directly from the UI
|
* You can now view and manage application stacks directly from the UI
|
||||||
|
* You can now view cluster and node level resource usage metrics
|
||||||
* When updating a service, the UI now shows more information about the service status
|
* When updating a service, the UI now shows more information about the service status
|
||||||
* Rolling update for services now have `failure-action` which you can use to
|
* Rolling update for services now have `failure-action` which you can use to
|
||||||
* Several improvements to service lifecycle management
|
* Several improvements to service lifecycle management
|
||||||
|
|
@ -48,9 +50,9 @@ Docker Engine 1.13.1 in the nodes that you plan to manage with UCP.
|
||||||
* You can now customize session timeouts in the authentication settings page
|
* You can now customize session timeouts in the authentication settings page
|
||||||
* Can now mount `tmpfs` or existing local volumes to a service when deploying
|
* Can now mount `tmpfs` or existing local volumes to a service when deploying
|
||||||
services from the UI
|
services from the UI
|
||||||
* Added more tooltips to guide users
|
* Added more tooltips to guide users on the above features
|
||||||
|
|
||||||
**Bug Fixes**
|
**Bug fixes**
|
||||||
|
|
||||||
* Core
|
* Core
|
||||||
* HTTP routing mesh can now be enabled or reconfigured when UCP is configured
|
* HTTP routing mesh can now be enabled or reconfigured when UCP is configured
|
||||||
|
|
@ -59,14 +61,10 @@ Docker Engine 1.13.1 in the nodes that you plan to manage with UCP.
|
||||||
to open up on the cluster
|
to open up on the cluster
|
||||||
* Fixed an issue in which UCP install occasionally failed with the error
|
* Fixed an issue in which UCP install occasionally failed with the error
|
||||||
"failed to change temp password"
|
"failed to change temp password"
|
||||||
* Defining multiple HRM networks with overlapping subnets now correctly causes
|
|
||||||
the HTTP Routing Mesh `ucp-hrm` service to fail.
|
|
||||||
* Fixed an issue where multiple rapid updates of HTTP Routing Mesh configuration
|
* Fixed an issue where multiple rapid updates of HTTP Routing Mesh configuration
|
||||||
would not register correctly
|
would not register correctly
|
||||||
* With HTTP Routing Mesh, using the "default" backend option with an empty
|
* Demoting a manager while in HA configuration no longer causes the `ucp-auth-api`
|
||||||
external route now works correctly
|
container to provide errors
|
||||||
* Volumes label-based access control now correctly supports volumes created
|
|
||||||
via the `mount` format flag
|
|
||||||
|
|
||||||
* UI/UX
|
* UI/UX
|
||||||
* When creating a user, pressing enter on keyboard no longer causes problems
|
* When creating a user, pressing enter on keyboard no longer causes problems
|
||||||
|
|
@ -74,10 +72,16 @@ Docker Engine 1.13.1 in the nodes that you plan to manage with UCP.
|
||||||
* Installing DTR no longer fails when "Enable scheduling on UCP controllers and
|
* Installing DTR no longer fails when "Enable scheduling on UCP controllers and
|
||||||
DTR nodes" is unchecked.
|
DTR nodes" is unchecked.
|
||||||
* Publishing a port to both TCP and UDP in a service via UI now works correctly
|
* Publishing a port to both TCP and UDP in a service via UI now works correctly
|
||||||
* Nodes now stay sorted after clicking a parameter to sort by in the Nodes screen
|
|
||||||
|
**Known issues**
|
||||||
|
|
||||||
|
|
||||||
**Version Compatibility**
|
The `docker stats` command is sometimes wrongly reporting high CPU usage.
|
||||||
|
Use the `top` command to confirm the real CPU usage of your node.
|
||||||
|
[Learn more](https://github.com/docker/docker/issues/28941).
|
||||||
|
|
||||||
|
|
||||||
|
**Version compatibility**
|
||||||
|
|
||||||
UCP 2.1 requires minimum versions of the following Docker components:
|
UCP 2.1 requires minimum versions of the following Docker components:
|
||||||
|
|
||||||
|
|
|
||||||
Loading…
Reference in New Issue