centersl/docker-docs
1
0
Fork 0
mirror of https://github.com/docker/docs.git synced 2026-04-03 01:38:58 +07:00
Code Issues Packages Projects Releases Wiki Activity

Update release-notes.md

Browse Source 
editorial crx
This commit is contained in:
L-Hudson
2019-01-30 19:39:25 -05:00
committed by GitHub
parent 81fe9158db
commit cafef334f2
1 changed files with 33 additions and 33 deletions
Download Patch File Download Diff File Expand all files Collapse all files

66
ee/ucp/release-notes.md
View File

@@ -52,8 +52,8 @@ upgrade your installation to the latest release.
enable this feature in Admin Settings -> SAML Settings.
### Audit Logging
* UCP Audit logging is now controlled via the UCP Configuration file, it is also
now configurable within the UCP UI. (#15466)
* UCP Audit logging is now controlled through the UCP Configuration file; it is also
now configurable within the UCP web interface. (#15466)
### Bug Fixes
* Core
@@ -99,7 +99,7 @@ Admins can now enable audit logging in the UCP config. This logs all incoming us
### Authentication
Admins can configure UCP to use a SAML-enabled identity provider for user authentication. If enabled, users who log into the UCP web interface are redirected to the identity provider's website to log in. Upon log in, users are redirected back to the UCP web interface, authenticated as the user chosen. For more information, see [Enable SAML authentication](https://docs.docker.com/ee/ucp/admin/configure/enable-saml-authentication/).
Admins can configure UCP to use a SAML-enabled identity provider for user authentication. If enabled, users who log into the UCP web interface are redirected to the identity provider's website to log in. Upon login, users are redirected back to the UCP web interface, authenticated as the user chosen. For more information, see [Enable SAML authentication](https://docs.docker.com/ee/ucp/admin/configure/enable-saml-authentication/).
### Metrics
@@ -261,7 +261,7 @@ The following features are deprecated in UCP 3.1.
### Known Issue
* When you are upgrading from UCP 3.0.3 or 3.0.4, you must manually pull
`docker/ucp-agent:3.0.5` in the images section of the web UI before upgrading.
`docker/ucp-agent:3.0.5` in the images section of the web interface before upgrading.
Alternately, you can just `docker pull docker/ucp-agent:3.0.5` on every manager node.
This issue is fixed in 3.0.5. Any upgrade from 3.0.5 or above should work without
manually pulling the images.
@@ -278,7 +278,7 @@ The following features are deprecated in UCP 3.1.
### Known Issue
* You must manually pull `docker/ucp-agent:3.0.4` in the images section of the web UI before upgrading. Alternately, you can just pull `docker/ucp-agent:3.0.4` on every manager node.
* You must manually pull `docker/ucp-agent:3.0.4` in the images section of the web interface before upgrading. Alternately, you can just pull `docker/ucp-agent:3.0.4` on every manager node.
## 3.0.3
@@ -300,7 +300,7 @@ The following features are deprecated in UCP 3.1.
* Calico is upgraded to 3.0.8
* Compose for Kubernetes logging improvements
* Fixes an issue where backups would fail if UCP was not licensed.
* Fixes an issue where DTR admins are missing the Full Control Grant against /Shared Collection even though they have logged in at least once to the UI.
* Fixes an issue where DTR admins are missing the Full Control Grant against /Shared Collection even though they have logged in at least once to the web interface.
* Add support for bind mount volumes to kubernetes stacks and fixes sporadic errors in kubernetes stack validator that would incorrectly reject stacks.
@@ -374,7 +374,7 @@ Azure Disk when installing UCP with the `--cloud-provider` option.
iptables -t filter -D KUBE-FIREWALL -m comment --comment "kubernetes firewall for dropping marked packets" -m mark --mark 0x8000/0x8000 -j DROP
```
* `ucp-kube-controller-manager` emits a large number of container logs.
* Excessive delay is seen when sending `docker service ls` via UCP client
* Excessive delay is seen when sending `docker service ls` through UCP client
bundle on a cluster that is running thousands of services.
* Inter-node networking may break on Kubernetes pods while the `calico-node`
pods are being upgraded on each node. This may cause up to a few minutes of
@@ -426,8 +426,8 @@ Interlock backend.
This adds increased performance, stability, and new features including SSL Termination,
Contextual Path-based Routing, Websocket Support, and Canary Application Instance
deployments. Existing Hostname Routing Mesh (HRM) labels (and newly added labels
with the old format) will automatically migrate to the new format. It is strongly
recommended to use the new format for new applications in order to take advantage
with the old format) will automatically migrate to the new format. We strongly
recommend you use the new format for new applications in order to take advantage
of the new features. [Learn more](https://docs.docker.com/ee/ucp/interlock/).
### Storage
@@ -464,7 +464,7 @@ will be available in future releases.
### Known issues
* Platform support
* Kubernetes is not yet supported for Windows based workloads. Use Swarmkit for
* Kubernetes is not yet supported for Windows-based workloads. Use Swarmkit for
Windows based workloads instead.
* EE 2.0 is not yet supported in IBM Z platforms.
* Upgrade
@@ -496,7 +496,7 @@ will be available in future releases.
The cluster upgrade completes, and Swarm workloads work, but Kubernetes networking
will be down.
* Management
* If upgrading UCP through the UI, UCP will not check to ensure the manager node
* If upgrading UCP through the web interface, UCP will not check to ensure the manager node
has the minimum memory required of 4 GB. Upgrading through the CLI does check for
this requirement.
* Putting a node in `drain` mode currently removes only Swarm workloads, and not
@@ -523,11 +523,11 @@ will be available in future releases.
The following functionality has been deprecated with UCP 3.0.0 and will be
unavailable in the next UCP feature release.
* The web UI is going to stop supporting users to deploy stacks with basic
* The web interface is going to stop supporting users to deploy stacks with basic
containers. You should update your Compose files to version 3, and deploy your
stack as a Swarm service or Kubernetes workload.
* The option to integrate with a remote Syslog system is going to be removed
from the UCP web UI. You can configure Docker Engine for this.
from the UCP web interface. You can configure Docker Engine for this.
* The option to configure a rescheduling policy for basic containers is
deprecated. Deploy your applications as Swarm services or Kubernetes workloads.
@@ -548,7 +548,7 @@ deprecated. Deploy your applications as Swarm services or Kubernetes workloads.
* Core
* Significantly reduced database load in environments with a lot of concurrent and repeated API requests by the same user.
* Added the ability to set custom HTTP response headers to be returned by the UCP Controller API Server.
* UI
* Web interface
* Fixed stack creation for non admin user when UCP uses a custom controller port.
## Version 2.2.14
@@ -568,7 +568,7 @@ deprecated. Deploy your applications as Swarm services or Kubernetes workloads.
* Resolved an issue where LDAP sync jobs would crash when handling an org admin search result which does not correspond to an existing user. (docker/escalation#784 #docker/escalation#888)
* Fixed an issue that caused RethinkDB client lock contention. (docker/escalation#902 and docker/escalation#906)
* UI
* Web Interface
* Fixed an issue that prevented "Per User Limit" on Admin Settings from working. (docker/escalation#639)
## Version 2.2.13
@@ -614,8 +614,8 @@ deprecated. Deploy your applications as Swarm services or Kubernetes workloads.
* Fixed an issue that raises `ucp-kv` collection error with unnamed volumes.
* UI
* Fixed an issue that causes UI to not parse volume options correctly.
* Fixed an issue that prevents the user from deploying stacks via UI.
* Fixed an issue that causes the web interface to not parse volume options correctly.
* Fixed an issue that prevents the user from deploying stacks through the web interface.
## Version 2.2.10
@@ -629,7 +629,7 @@ deprecated. Deploy your applications as Swarm services or Kubernetes workloads.
* UI
* Users can now set log driver name and options on both create and update
service screens.
* Fixed an issue that causes legacy collections on services to break UI. Now
* Fixed an issue that causes legacy collections on services to break the web interface. Now
legacy collections are properly prepended with "/Shared/Legacy/".
* Fixed an issue that causes service counts in status summary to be shown
incorrectly.
@@ -653,7 +653,7 @@ deprecated. Deploy your applications as Swarm services or Kubernetes workloads.
### Known Issue
* Excessive delay is seen when sending `docker service ls` via UCP client
* Excessive delay is seen when sending `docker service ls` through a UCP client
bundle on a cluster that is running thousands of services.
@@ -665,7 +665,7 @@ deprecated. Deploy your applications as Swarm services or Kubernetes workloads.
* Security
* Fixed an issue that allows users to incorrectly interact with local volumes.
* Fixed an issue where setting minimum TLS version that causes `ucp-agent` to
* Fixed an issue where setting minimum TLS version causes `ucp-agent` to
keep restarting on worker nodes.
* Core
@@ -689,7 +689,7 @@ deprecated. Deploy your applications as Swarm services or Kubernetes workloads.
### New features
* Security
* Default TLS connections to TLS 1.2, and allow users to configure the minimum
* Default TLS connections to TLS 1.2, and allows users to configure the minimum
TLS version used by the UCP controller.
* Support and troubleshoot
* The support dump now includes the output of `dmesg`.
@@ -784,14 +784,14 @@ for volumes.
* Additional translations added for internationalization.
* UI for adding users to teams simplified.
* The grant list can now sorted and pagination in the grants view has been improved. The grants view previously had glitches on systems with many grants.
* Fixed problem where UI would hang when pulling images.
* Fixed problem where the web interface would hang when pulling images.
* "Max failure ratio" and "Failure action" re-introduced in service definitions. These settings were not available in UCP 2.2, but were available in previous UCP versions.
* Collection labels are no longer applied to UCP system services. UCP previously auto-applied labels, which was confusing.
### Known issues
* Docker currently has limitations related to overlay networking and services using VIP-based endpoints. These limitations apply to use of the HTTP Routing Mesh (HRM). HRM users should familiarize themselves with these limitations. In particular, HRM may encounter virtual IP exhaustion (as evidenced by `failed to allocate network IP for task` Docker log messages). If this happens, and if the HRM service is restarted or rescheduled for any reason, HRM may fail to resume operation automatically. See the Docker EE 17.06-ee5 release notes for details.
* The Swarm admin UI for UCP versions 2.2.0 and later contain a bug. If used with Docker Engine version 17.06.2-ee5 or earlier, attempting to update "Task History Limit", "Heartbeat Period" and "Node Certificate Expiry" settings using the UI will cause the cluster to crash on next restart. Using UCP 2.2.X and Docker Engine 17.06-ee6 and later, updating these settings will fail (but not cause the cluster to crash). Users are encouraged to update to Docker Engine version 17.06.2-ee6 and later, and to use the Docker CLI (instead of the UCP UI) to update these settings. Rotating join tokens works with any combination of Docker Engine and UCP versions. Docker Engine versions 17.03 and earlier (which use UCP version 2.1 and earlier) are not affected by this problem.
* The Swarm admin web interface for UCP versions 2.2.0 and later contain a bug. If used with Docker Engine version 17.06.2-ee5 or earlier, attempting to update "Task History Limit", "Heartbeat Period" and "Node Certificate Expiry" settings using the UI will cause the cluster to crash on next restart. Using UCP 2.2.X and Docker Engine 17.06-ee6 and later, updating these settings will fail (but not cause the cluster to crash). Users are encouraged to update to Docker Engine version 17.06.2-ee6 and later, and to use the Docker CLI (instead of the UCP UI) to update these settings. Rotating join tokens works with any combination of Docker Engine and UCP versions. Docker Engine versions 17.03 and earlier (which use UCP version 2.1 and earlier) are not affected by this problem.
## Version 2.2.3
@@ -843,7 +843,7 @@ for volumes.
* Searching for images in the UCP images UI doesn't work.
* Removing a stack may leave orphaned volumes.
* Storage metrics are not available for Windows.
* You can't create a bridge network from the web UI. As a workaround use
* You can't create a bridge network from the web interface. As a workaround use
`<node-name>/<network-name>`.
@@ -897,8 +897,8 @@ a 1:1:1 mapping of a Subject, a Role, and a Collection:
* Role: A set of permissions. In addition to the existing predefined roles,
admins can now create custom roles with their choice of permissions taken
from the full Docker API.
* Collection: A group of containers or container-based resources (e.g. volumes,
networks, secrets, etc.). Collections have a hierarchical directory-like structure
* Collection: A group of containers or container-based resources (for example, volumes,
networks, secrets). Collections have a hierarchical directory-like structure
and replace the old access control labels from the previous system (though they
still use labels in the CLI).
* [Read the documentation](access-control/index.md#transition-from-ucp-21-access-control)
@@ -921,9 +921,9 @@ Windows-based containerized applications on the cluster.
* Support for UCP workers running on IBM Z systems with RHEL 7.3, Ubuntu 16.04,
and SLES 12.
* UCP now provides a public, stable API for cluster configuration and access control,
and the API is fully interactive within the UCP UI.
and the API is fully interactive within the UCP web interface.
* Support for using services with macvlan networks and configuring network scope in UI.
* The UCP UI has been redesigned for ease-of-use and data management:
* The UCP web interface has been redesigned for ease-of-use and data management:
* Redesigned dashboard with time-series historical graphs for usage metrics.
* Compact layout to more easily view resource information at a glance.
* Detail panels for resources no longer slide out and cover the main panel.
@@ -932,26 +932,26 @@ and the API is fully interactive within the UCP UI.
### Known issues
* UI issues:
* Cannot currently remove nodes using UCP UI. Workaround is to remove from CLI
* Cannot currently remove nodes using UCP web interface. Workaround is to remove from CLI
instead.
* Search does not function correctly for images.
* Cannot view label constraints from a collection's details pages. Workaround
is to view by editing the collection.
* Certain config changes to UCP make take several minutes to update after making
changes in the UI. In particular this affects LDAP/AD configuration changes.
changes in the web interface. In particular this affects LDAP/AD configuration changes.
* Turning `LDAP Enabled` from "Yes" to "No" disables the save button. Workaround
is to do a page refresh which completes the configuration change.
* Removing stacks from the UI may cause certain resources to not be deleted,
including networks or volumes. Workaround is to delete the resources directly.
* When you create a network and check 'Enable hostname based routing', the web
UI doesn't apply the HRM labels to the network. As a workaround,
interface doesn't apply the HRM labels to the network. As a workaround,
[create the network using the CLI](https://docs.docker.com/datacenter/ucp/2.2/guides/user/services/use-domain-names-to-access-services/#service-labels).
* The web UI does not currently persist changes to session timeout settings.
* The web interface does not currently persist changes to session timeout settings.
As a workaround you can update the settings from the CLI, by [adapting these instructions for the
session timeout](https://docs.docker.com/datacenter/ucp/2.2/guides/admin/configure/external-auth/enable-ldap-config-file/).
* docker/ucp
* The `support` command does not currently produce a valid support dump. As a
workaround you can download a support dumps from the web UI.
workaround you can download a support dumps from the web interface.
* Windows issues
* Disk related metrics do not display for Windows worker nodes.
* If upgrading from an existing deployment, ensure that HRM is using a non-encrypted