UCP release notes

Here you can learn about new features, bug fixes, breaking changes, and known issues for the latest UCP version. You can then use the upgrade instructions to upgrade your installation to the latest release.

• Version 3.1
• Version 3.0
• Version 2.2

Version 3.1

3.1.6

(2019-04-11)

Kubernetes

• Updated Kubernetes to version 1.11.9.

Networking

• Updated Calico to version 3.5.3.

Authentication and Authorization

• Accessing the ListAccount API endpoint now requires an admin user. Accessing the GetAccount API endpoint now requires an admin user, the actual user, or a member of the organization being inspected. ENGORC-100

Known Issues

• Upgrading from UCP 3.1.4 to 3.1.5 causes missing Swarm placement constraints banner for some Swarm services (ENGORC-2191). This can cause Swarm services to run unexpectedly on Kubernetes nodes. See https://www.docker.com/ddc-41 for more information.
  • Workaround: Delete any ucp-*-s390x Swarm services. For example, ucp-auth-api-s390x.
• There are important changes to the upgrade process that, if not correctly followed, can impact the availability of applications running on the Swarm during uprades. These constraints impact any upgrades coming from any Docker Engine version before 18.09 to version 18.09 or greater. For more information about about upgrading Docker Enterprise to version 2.1, see Upgrade Docker.
• To deploy Pods with containers using Restricted Parameters, the user must be an admin and a service account must explicitly have a ClusterRoleBinding with cluster-admin as the ClusterRole. Restricted Parameters on Containers include:
  • Host Bind Mounts
  • Privileged Mode
  • Extra Capabilities
  • Host Networking
  • Host IPC
  • Host PID
• If you delete the built-in ClusterRole or ClusterRoleBinding for cluster-admin, restart the ucp-kube-apiserver container on any manager node to recreate them. (#14483)
• Pod Security Policies are not supported in this release. (#15105)
• The default Kubelet configuration for UCP Manager nodes is expecting 4GB of free disk space in the /var partition. See System Requirements for details.

Components

3.1.5

2019-03-28

Kubernetes

• Updated Kubernetes to version 1.11.8. (ENGORC-2024)

Networking

• Updated Calico to version 3.5.2. (ENGORC-2045)

Authentication and Authorization

• Added LDAP Settings API to the list of publicly documented API endpoints. (ENGORC-98)
• Added a new exclude_server_identity_headers field to the UCP config. If set to true, the headers are not included in UCP API responses. (docker/orca#16039)
• Hid most of the UCP banners for non-admin users. (docker/orca#14631)
• When LDAP or SAML is enabled, provided admin users an option to disable managed password authentication, which includes login and creation of new users. (ENGORC-1999)

Bug Fixes

• Changed Interlock proxy service default update-action-failure to rollback. (ENGCORE-117)
• Added validation for service configuration label values. (ENGCORE-114)
• Fixed an issue with continuous interlock reconciliation if ucp-interlock service image does not match expected version. (ENGORC-2081)

Known Issues

• Upgrading from UCP 3.1.4 to 3.1.5 causes missing Swarm placement constraints banner for some Swarm services (ENGORC-2191). This can cause Swarm services to run unexpectedly on Kubernetes nodes. See https://www.docker.com/ddc-41 for more information.
  • Workaround: Delete any ucp-*-s390x Swarm services. For example, ucp-auth-api-s390x.
• There are important changes to the upgrade process that, if not correctly followed, can impact the availability of applications running on the Swarm during uprades. These constraints impact any upgrades coming from any Docker Engine version before 18.09 to version 18.09 or greater. For more information about about upgrading Docker Enterprise to version 2.1, see Upgrade Docker
• To deploy Pods with containers using Restricted Parameters, the user must be an admin and a service account must explicitly have a ClusterRoleBinding with cluster-admin as the ClusterRole. Restricted Parameters on Containers include:
  • Host Bind Mounts
  • Privileged Mode
  • Extra Capabilities
  • Host Networking
  • Host IPC
  • Host PID
• If you delete the built-in ClusterRole or ClusterRoleBinding for cluster-admin, restart the ucp-kube-apiserver container on any manager node to recreate them. (#14483)
• Pod Security Policies are not supported in this release. (#15105)
• The default Kubelet configuration for UCP Manager nodes is expecting 4GB of free disk space in the /var partition. See System Requirements for details.

Components

3.1.4

2019-02-28

New platforms

• Added support for SLES 15.
• Added support for Oracle 7.6.

Kubernetes

• Kubernetes has been updated to version 1.11.7. (docker/orca#16157)

Bug Fixes

• Bump the Golang version that is used to build UCP to version 1.10.8. (docker/orca#16068)
• Fixed an issue that caused UCP upgrade failure to upgrade with Interlock deployment. (docker/orca#16009)
• Fixed an issue that caused Windows node ucp-agent(s) to constantly reboot when audit logging is enabled. (docker/orca#16122)
• Fixed an issue to ensure that non-admin user actions (with the RestrictedControl role) against RBAC resources are read-only. (docker/orca#16121)
• Fixed an issue to prevent UCP users from updating services with a port that conflicts with the UCP controller port. (escalation#855)
• Fixed an issue to validate Calico certs expiration dates and update accordingly. (escalation#981)
• Kubelet no longer deletes images, starting with the oldest unused images, after exceeding 85% disk space utilization. This was an issue in air-gapped environments. (docker/orca#16082)

Enhancements

• Changed packaging and builds for UCP to build bootstrapper last. This avoids the “upgrade available” banner on all UCPs until the entirety of UCP is available.

Known Issues

• Newly added Windows node reports “Awaiting healthy status in classic node inventory”. Learn more.
• There are important changes to the upgrade process that, if not correctly followed, can impact the availability of applications running on the Swarm during uprades. These constraints impact any upgrades coming from any Docker Engine version before 18.09 to version 18.09 or greater. For more information about about upgrading Docker Enterprise to version 2.1, see Upgrade Docker
• In the UCP web interface, LDAP settings disappear after submitting them. However, the settings are properly saved. (docker/orca#15503)
• To deploy Pods with containers using Restricted Parameters, the user must be an admin and a service account must explicitly have a ClusterRoleBinding with cluster-admin as the ClusterRole. Restricted Parameters on Containers include:
  • Host Bind Mounts
  • Privileged Mode
  • Extra Capabilities
  • Host Networking
  • Host IPC
  • Host PID
• If you delete the built-in ClusterRole or ClusterRoleBinding for cluster-admin, restart the ucp-kube-apiserver container on any manager node to recreate them. (docker/orca#14483)
• Pod Security Policies are not supported in this release. (docker/orca#15105)
• The default Kubelet configuration for UCP Manager nodes is expecting 4GB of free disk space in the /var partition. See System Requirements for details.

Components

3.1.3

2019-01-29

New platforms

• Added support for Windows Server 2019 and Windows Server 1809. (docker/orca#15810)
• Added support for RHEL 7.6 with Devicemapper and Overlay2 storage drivers. (docker/orca#15535)
• Added support for Oracle Enterprise Linux 7.6 with Overlay2 storage driver. (docker/orca#15791)

Networking

• Upgraded Calico to version 3.5. (#15884)

Bug Fixes

• Fixed system hang following UCP backup and docker daemon shutdown. (docker/escalation#841)
• Non-admin users can no longer create PersistentVolumes that mount host directories. (docker/orca#15936)
• Added support for the limit arg in docker ps. (docker/orca#15812)
• Fixed an issue with ucp-proxy health check. (docker/orca#15814, docker/orca#15813, docker/orca#16021, docker/orca#15811)
• Fixed an issue with manual creation of a ClusterRoleBinding or RoleBinding for User or Group subjects requiring the ID of the user, organization, or team. (docker/orca#14935)
• Fixed an issue in which Kube Rolebindings only worked on UCP User ID and not UCP username. (docker/orca#14935)

Known issue

• By default, Kubelet begins deleting images, starting with the oldest unused images, after exceeding 85% disk space utilization. This causes an issue in an air-gapped environment. (docker/orca#16082)

Components

3.1.2

2019-01-09

Authentication and Authorization

• SAML Single Logout is now supported in UCP.
• Identity Provider initiated SAML Single Sign-on is now supported in UCP. The admin can enable this feature in Admin Settings -> SAML Settings.

Audit Logging

• 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
  • Significantly reduced database load in environments with a lot of concurrent and repeated API requests by the same user. (docker/escalation#911)
  • UCP backend will now complain when a service is created/updated if the com.docker.lb.network label is not correctly specified. (docker/orca#15015)
  • LDAP group member attribute is now case insensitive. (docker/escalation#917)
• Interlock
  • Interlock headers can now be hidden. (escalation#833)
  • Now upgrading Interlock will also upgrade interlock proxy and interlock extension as well (escalation/871)
  • Added support for ‘VIP’ backend mode, in which the Interlock proxy connects to the backend service’s Virtual IP instead of load-balancing directly to each task IP. (docker/interlock#206) (escalation/920)

Known Issues

• In the UCP web interface, LDAP settings disappear after submitting them. However, the settings are properly saved. (docker/orca#15503)
• By default, Kubelet begins deleting images, starting with the oldest unused images, after exceeding 85% disk space utilization. This causes an issue in an air-gapped environment. (docker/orca#16082)

Components

3.1.1

(2018-12-04)

• To address CVE-2018-1002105, a critical security issue in the Kubernetes API Server, Docker is using Kubernetes 1.11.5 for UCP 3.1.1.

Components

3.1.0

2018-11-08

Bug Fixes

• Swarm placement constraint warning banner no longer shows up for ucp-auth services (#14539)
• “update out of sequence” error messages no longer appear when changing admin settings (#7093)
• Kubernetes namespace status appears in the web interface (#14526)
• UCP Kubernetes compose components always run on managers (#14208)
• docker network ls --filter id=<id> now works with a UCP client bundle (#14840)
• Collection deletes are correctly blocked if there is a node in the collection (#13704)

New Features

Kubernetes

• Kubernetes is updated to version 1.11.2.
• Kubernetes native RBAC feature manages access control for Kubernetes resources. Users can now create roles for Kubernetes APIs using Kubernetes Role and ClusterRole objects in the Kubernetes API. They can also grant permissions to users and service accounts with the RoleBinding and ClusterRoleBinding objects. The web interface for Kubernetes RBAC reflects these changes. Your old Kubernetes grants and roles will be automatically migrated during the UCP upgrade.

Logging

Admins can now enable audit logging in the UCP config. This logs all incoming user-initiated requests in the ucp-controller logs. Admins can choose whether to log only metadata for incoming requests or the full request body as well. For more information, see Create UCP audit logs.

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.

Metrics

• The ucp-metrics Prometheus server (used to render charts in the UCP interface) was engineered from a container on manager nodes to a Kubernetes daemonset. This lets admins change the daemonset’s scheduling rules so that it runs on a set of worker nodes instead of manager nodes. Admins can designate certain UCP nodes to be metrics server nodes, freeing up resources on manager nodes. For more information, see Collect UCP cluster metrics with Prometheus.
• The UCP controller has a /metricsdiscovery endpoint so users can connect their own Prometheus instances to scrape UCP metrics data.

UCP web interface

• If you enable single sign-on for a DTR instance with UCP, the UCP web interface shows image vulnerability data for images in that DTR instance. Containers and services that use images from that DTR instance show any vulnerabilities DTR detects.
• The UCP web interface is redesigned to offer larger views for viewing individual resources, with more information for Kubernetes resources.

Configs

• UCP now stores its configurations in its internal key-value store instead of in a Swarm configuration so changes can propagate across the cluster more quickly.
• You can now use the custom_api_server_headers field in the UCP configuration to set arbitrary headers that are included with every UCP response.

API updates

There are several backward-incompatible changes in the Kubernetes API that may affect user workloads. They are:

• A compatibility issue with the allowPrivilegeEscalation field that caused policies to start denying pods they previously allowed was fixed. If you defined PodSecurityPolicy objects using a 1.8.0 client or server and set allowPrivilegeEscalation to false, these objects must be reapplied after you upgrade.
• These changes are automatically updated for taints. Tolerations for these taints must be updated manually. Specifically, you must:
  • Change node.alpha.kubernetes.io/notReady to node.kubernetes.io/not-ready
  • Change node.alpha.kubernetes.io/unreachable to node.kubernetes.io/unreachable For more information about taints and tolerations, see Taints and Tolerations.
• JSON configuration used with kubectl create -f pod.json containing fields with incorrect casing are no longer valid. You must correct these files before upgrading. When specifying keys in JSON resource definitions during direct API server communication, the keys are case-sensitive. A bug introduced in Kubernetes 1.8 caused the API server to accept a request with incorrect case and coerce it to correct case, but this behaviour has been fixed in 1.11 so the API server will again enforce correct casing. During this time, the kubectl tool continued to enforce case-sensitive keys, so users that strictly manage resources with kubectl will be unaffected by this change.
• If you have a pod with a subpath volume PVC, there’s a chance that after the upgrade, it will conflict with some other pod; see this pull request. It’s not clear if this issue will just prevent those pods from starting or if the whole cluster will fail.

Known issues

• There are important changes to the upgrade process that, if not correctly followed, can impact the availability of applications running on the Swarm during uprades. These constraints impact any upgrades coming from any Docker Engine version before 18.09 to version 18.09 or greater. For more information about about upgrading Docker Enterprise to version 2.1, see Upgrade Docker
• In the UCP web interface, LDAP settings disappear after submitting them. However, the settings are properly saved. (#15503)
• You must use the ID of the user, organization, or team if you manually create a ClusterRoleBinding or RoleBinding for User or Group subjects. (#14935)
  • For the User subject Kind, the Name field contains the ID of the user.
  • For the Group subject Kind, the format depends on whether you are create a Binding for a team or an organization:
    • For an organization, the format is org:{org-id}
    • For a team, the format is team:{org-id}:{team-id}
• To deploy Pods with containers using Restricted Parameters, the user must be an admin and a service account must explicitly have a ClusterRoleBinding with cluster-admin as the ClusterRole. Restricted Parameters on Containers include:
  • Host Bind Mounts
  • Privileged Mode
  • Extra Capabilities
  • Host Networking
  • Host IPC
  • Host PID
• If you delete the built-in ClusterRole or ClusterRoleBinding for cluster-admin, restart the ucp-kube-apiserver container on any manager node to recreate them. (#14483)
• Pod Security Policies are not supported in this release. (#15105)
• The default Kubelet configuration for UCP Manager nodes is expecting 4GB of free disk space in the /var partition. See System Requirements for details.

Deprecated features

The following features are deprecated in UCP 3.1.

• Collections

  • The ability to create a nested collection of more than 2 layers deep within the root /Swarm/ collection is now deprecated and will not be included in future versions of the product. However, current nested collections with more than 2 layers are still retained.

  • Docker recommends a maximum of two layers when creating collections within UCP under the shared cluster collection designated as /Swarm/. For example, if a production collection called /Swarm/production is created under the shared cluster collection, /Swarm/, then only one level of nesting should be created: /Swarm/production/app/. See Nested Collections for more details.

• Kubernetes
  • PersistentVolumeLabel admission controller is deprecated in Kubernetes 1.11. This functionality will be migrated to [Cloud Controller Manager](https://kubernetes.io/docs/tasks/administer-cluster/running-cloud-controller/](https://kubernetes.io/docs/tasks/administer-cluster/running-cloud-controller/)
  • --cni-install-url is deprecated in favor of --unmanaged-cni

Components

Version 3.0

3.0.10

2019-02-28

Bug Fixes

• Bump the Golang version that is used to build UCP to version 1.10.8.
• Prevent UCP users from updating services with a port that conflicts with the UCP controller port. (escalation#855)
• Fixed an issue that causes UCP fail to upgrade with Interlock deployment. (docker/orca/#16009)
• Validate Calico certs expiration date and update accordingly. (escalation#981)

3.0.9

2018-01-29

New platforms

• Added support for RHEL 7.6 with Devicemapper and Overlay2 storage drivers. (docker/orca#15996)

Bug fixes

• Upgrading Interlock now also upgrades interlock proxy and interlock extension. (docker/escalation/871)
• Non-admin users can no longer create PersistentVolumes that mount host directories. (#15936)
• Added support for the limit arg in docker ps. (#15812)

Known issue

• By default, Kubelet begins deleting images, starting with the oldest unused images, after exceeding 85% disk space utilization. This causes an issue in an air-gapped environment.

Components

3.0.8

2019-01-09

Bug fixes

• Core
  • Significantly reduced database load in environments with a lot of concurrent and repeated API requests by the same user. (docker/escalation#911)
  • Added the ability to set custom HTTP response headers to be returned by the UCP Controller API Server. (docker/orca#10733)
  • UCP backend will now complain when a service is created/updated if the com.docker.lb.network label is not correctly specified. (docker/orca#15015)
  • LDAP group member attribute is now case insensitive. (docker/escalation#917)
  • Fixed an issue that caused a system hang after UCP backup and the attempted shutdown of the Docker daemon to perform a swarm backup. /dev/shm is now unmounted when starting the kubelet container. (docker/orca#15672, docker/escalation#841)
• Interlock
  • Interlock headers can now be hidden. (docker/escalation#833)
  • Respect com.docker.lb.network labels and only attach the specified networks to the Interlock proxy. (docker/interlock#169)
  • Add support for ‘VIP’ backend mode, in which the Interlock proxy connects to the backend service’s Virtual IP instead of load-balancing directly to each task IP. (docker/interlock#206, escalation/920)

Components

3.0.7

2018-12-04

• To address CVE-2018-1002105, a critical security issue in the Kubernetes API Server, Docker is using a custom build of Kubernetes 1.8.15 for UCP 3.0.7.

Components

3.0.6

2018-10-25

Bug fixes

• Core
  • Updated Kubernetes to version 1.8.15.
  • Resolved an issue where LDAP sync jobs terminated when processing an org admin search result that did 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)
  • Fixed an issue that caused Azure IPAM to not release addresses. (docker/escalation#815)
  • Fixed an issue that caused unsuccessful installation of UCP on Azure. (docker/escalation#863)
  • Fixed an issue that caused the Interlock proxy service to keep restarting. (docker/escalation#814)
  • Fixed an issue that caused Kubernetes DNS to not work. (#14064, #11981)
  • Fixed an issue that caused “Missing swarm placement constraints” warning banner to appear unnecessarily. (docker/orca#14539)
• Security
  • Fixed libcurl vulnerability in RethinkDB image. (docker/orca#15169)
• UI
  • Fixed an issue that prevented “Per User Limit” on Admin Settings from working. (docker/escalation#639)

Components

3.0.5

2018-08-30

Bug fixes

• Security
  • Fixed a critical security issue to prevent UCP from accepting certificates from the system pool when adding client CAs to the server that requires mutual authentication.

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 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.

Components

3.0.4

2018-08-09

Bug fixes

• Security
  • Fixed a critical security issue where the LDAP bind username and password were stored in cleartext on UCP hosts. Please refer to this KB article for proper implementation of this fix.

Known Issue

• 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.

Components

3.0.3

2018-07-26

New platforms

• UCP now supports running Windows Server 1803 workers
  • Server 1803 ingress routing, VIP service discovery, and named pipe mounting are not supported in this release.
  • Offline bundles ucp_images_win_1803_3.0.3.tar.gz have been added.
• UCP 3.0.3 now supports IBM Z (s390x) as worker nodes on 3.0.x for SLES 12 SP 3. Interlock is currently not supported for 3.0.x on Z.

Bug Fixes

• Core
  • Optimize swarm service read api calls through UCP
  • Fixes an issue where some UCP Controller API calls may hang indefinitely.
  • Default Calico MTU set to 1480
  • 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 web interface.
  • Add support for bind mount volumes to kubernetes stacks and fixes sporadic errors in kubernetes stack validator that would incorrectly reject stacks.

Components

3.0.2

2018-06-21

New Features

• UCP now supports running Windows Server 1709 workers
  • Server 1709 provides smaller Windows base image sizes, as detailed here
  • Server 1709 provides relaxed image compatibility requirements, as detailed here
  • Server 1709 ingress routing, VIP service discovery, and named pipe mounting are not supported in this release.
  • Offline bundle names are changed from ucp_images_win_3.0.1.tar.gz to ucp_images_win_2016_3.0.2.tar.gz and ucp_images_win_1709_3.0.2.tar.gz based on Windows Server versions.
• UCP now supports running RHEL 7.5. Please refer to the compatibility matrix.
• Added support for dynamic volume provisioning in Kubernetes for AWS EBS and Azure Disk when installing UCP with the --cloud-provider option.

Bug Fixes

• Core
  • Fixed an issue for anonymous volumes in Compose for Kubernetes.
  • Fixed an issue where a fresh install would have an initial per-user session limit of unlimited rather than the expected limit of 10 minutes.
  • Added separate resource types for Kubernetes subresources (e.g. pod/log) so that users can get separate permissions for those resources, as with the built-in Kubernetes RBAC authorizer. If you had a custom role with (for instance) Pod Get permissions, you may need to create a new custom role with permissions for each new subresource.
  • To deploy Pods with Privileged options, users now require a grant with the role Full Control for all namespaces.
  • The /api/ucp/config endpoint now includes default node orchestrator.
  • Added cni_mtu setting to UCP config for controlling MTU size in Calico.
  • When a route is not found, interlock now returns a 503 (the expected behavior) instead of a 404.
• UI/UX
  • Fixed an issue that causes LDAP configuration UI to not work properly.

Components

3.0.1

2018-05-17

Bug Fixes

• Core
  • Bumped Kubernetes version to 1.8.11.
  • Compose for Kubernetes now respects the specified port services are exposed on. This port must be in the NodePort range.
  • Kubernetes API server port is now configurable via --kube-apiserver-port flag at install or cluster_config.kube_apiserver_port in UCP config.
  • Fixed an issue where upgrade fails due to missing ucp-kv snapshots.
  • Fixed an issue where upgrade fails due to layer 7 routing issues.
  • ucp-interlock-proxy no longer tries to schedule components on Windows nodes.
  • Fixed an issue where a Kubernetes networking failure would not stop UCP from installing successfully.
  • Fixed an issue where encrypted overlay networks could not communicate on firewalled hosts.
  • Fixed an issue where Pod CIDR and Node IP values could conflict at install Installation no longer fails if an empty PodCIDR value is set in the UCP config at install time. Instead, it falls back to default CIDR.
• UI/UX
• Fixed an issue where UCP banners redirected to older UCP 2.2 documentation.

Known issues

• Encrypted overlay networks may not work after upgrade from 3.0.0. Apply the following to all the nodes after the upgrade.

    iptables -t nat -D KUBE-MARK-DROP -j MARK --set-xmark 0x8000/0x8000
    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.
• 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 networking disruption for pods on each node during the upgrade process, depending on how quickly calico-node gets upgraded on those nodes.
• ucp-interlock-proxy may fail to start when two or more services are configured with two or more backend hosts. You can use this workaround.

### Components

Version 3.0.0

2018-04-17

The UCP system requirements were updated with 3.0.0. Make sure to check the system requirements before upgrading.

Orchestration

• UCP now supports Kubernetes as an orchestrator, in addition to the existing Swarmkit and “classic” Swarm orchestrators. Kubernetes system components are automatically deployed on all manager and Linux worker nodes managed by UCP. Learn more about Kubernetes support.
• Worker nodes running Linux on amd64 architectures can be configured to run only Swarm workloads, only Kubernetes workloads, or mixed workloads. Manager nodes are by default Mixed in order to support Swarm and Kubernetes system components. However, it is not recommended to run Worker nodes as Mixed due to potential resource contention issues.
• Users can deploy Kubernetes workloads through the web UI, and the CLI using a UCP client bundle and kubectl. Learn more.
• Users can now use Compose to deploy Kubernetes workloads from the web UI. Learn more.

Networking

• UCP includes Calico as the default CNI plugin for networking of Kubernetes applications. Learn more. The following Calico features are supported:
  • L3 IP-IP Overlay Data Path.
  • BGP control plane.
  • Calico IPAM.
  • Management of Calico CNI plugin lifecycle.
  • Kubernetes Network Policy. This is experimental in 3.0.0.
• You can now use layer 7 routing in your Kubernetes workloads by using an NGINX-based ingress controller. Learn more.
• Layer 7 routing for Swarmkit applications has been upgraded to use 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. We strongly recommend you use the new format for new applications in order to take advantage of the new features. Learn more.

Storage

• Support for NFS-based Kubernetes persistent volumes. Additional volume plugins will be available in future releases.

Security

• Role-based access control now supports Kubernetes resources. Learn more.
  • In addition to users, teams, organizations, and grants you can now use Kubernetes Service Accounts as a subject type. Learn more.
  • You can now create custom roles with Kubernetes API permissions. Default roles include Kubernetes API permissions based on their access type. As an example, View-Only contains Swarm and Kubernetes read-only API permissions.
  • In addition to collections, grants can now use Kubernetes Namespaces as a resource set type.
  • Admins can now link a Kubernetes namespace to a collection of nodes in order to isolate users and workloads between different nodes.
• Administrators can now enforce only running trusted images for both swarm and Kubernetes applications. Learn more
• API support for registering multiple UCP clusters to a single DTR for the purposes of signed image enforcement. Learn more.
• The Restricted Control role includes the User Impersonation Kubernetes action, which can allow a user to escalate to admin privileges if the role is granted against All Kubernetes Namespaces. For this version, we recommend that administrators do not grant the Restricted Control role against Kubernetes namespaces, and use custom roles instead. This issue does not affect any other roles in the system, or any of the grants using Restricted Control against collections.
• For increased security UCP now requires clients to use TLS version 1.2.

Known issues

• Platform support
  • 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
  • After upgrading to 3.0, UCP uses the 191.168.0.0/16 CIDR to allocate IPs for Kubernetes Pods. This option is customizable when doing a fresh installation, but not during an upgrade. As a workaround to configure this option, before upgrading, update the UCP configuration to include pod_cidr = "<ip>/<mask>" under the [cluster_config] option.
• CLI
  • Both Docker and kubectl CLIs report that UCP is running Kubernetes 1.8.2, when in fact it is running 1.8.9.
• Networking
  • Swarm encrypted overlay networks might not work as expected because default Kubernetes firewall rules are interfering with them. Learn more.
  • Calico networking for Kubernetes is not supported for Microsoft Azure. UCP leverages Azure networking and IPAM for control-plane and connectivity. Learn how to deploy EE 2.0 on Azure.
  • Azure IPAM will fail if nodes in the cluster are connected to different subnets. As a workaround ensure network setup avoids multiple subnets. This will be rectified in an upcoming patch release.
  • UCP Calico control-plane supports full-mesh BGP peering only at release-time. Calico control-plane may cause high CPU on nodes in clusters above 100 nodes. A route reflector based partial-mesh BGP control-plane will reduce CPU consumption when scaling past 100 nodes. Route-reflector configurations will be included in a future release.
  • In some deployments the kube-dns component won’t be able to resolve external domain names. Deploy a ConfigMap to work around this.
  • If you upgrade from UCP 2.x to UCP 3.x on Azure, Kubernetes networking doesn’t work. The cluster upgrade completes, and Swarm workloads work, but Kubernetes networking will be down.
• Management
  • 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 Kubernetes workloads. This will be fixed in a future release.
  • Kubernetes base image layer uses Ubuntu 16.04 which contains some known CVE vulnerabilities. These will be removed when the base image layer is updated.
  • Running docker system prune -a directly on individual worker nodes in the cluster will potentially delete UCP system images. This behavior will not occur if the prune command is run using a UCP client bundle.
  • Compose for Kubernetes only supports v3 or higher YAML files. Any older version YAML files will silently fail without errors.
  • Linking Kubernetes namespace to a collection of nodes in order to isolate Kubernetes workloads between different nodes is not working as expected. You can use this workaround.
  • Running kubectl get cs might show some internal UCP components as unhealthy when that’s not the case.
• Storage
  • UCP does not yet support dynamic volume provisioning (NFS volumes do not support this). This will change in future releases when more volume types are available.

Deprecation notice

The following functionality has been deprecated with UCP 3.0.0 and will be unavailable in the next UCP feature release.

• 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 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.

Components

Version 2.2

Version 2.2.17

2019-02-28

Bug Fixes

• Bump the Golang version that is used to build UCP to version 1.10.8.
• Prevent UCP users from updating services with a port that conflicts with the UCP controller port. (escalation#855)

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 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.
• Upgrading heterogeneous swarms from CLI may fail because x86 images are used instead of the correct image for the worker architecture.
• Agent container log is empty even though it’s running correctly.
• Rapid UI settings updates may cause unintended settings changes for logging settings and other admin settings.
• Attempting to load an (unsupported) tar.gz image results in a poor error message.
• 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 interface. As a workaround use <node-name>/<network-name>.

Version 2.2.16

2019-01-29

Bug fixes

• Added support for the limit argument in docker ps. (#15812)

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 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.
• Upgrading heterogeneous swarms from CLI may fail because x86 images are used instead of the correct image for the worker architecture.
• Agent container log is empty even though it’s running correctly.
• Rapid UI settings updates may cause unintended settings changes for logging settings and other admin settings.
• Attempting to load an (unsupported) tar.gz image results in a poor error message.
• 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 interface. As a workaround use <node-name>/<network-name>.

Version 2.2.15

2019-01-09

Bug fixes

• 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.
• Web interface
  • Fixed stack creation for non admin user when UCP uses a custom controller port.

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 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.
• Upgrading heterogeneous swarms from CLI may fail because x86 images are used instead of the correct image for the worker architecture.
• Agent container log is empty even though it’s running correctly.
• Rapid UI settings updates may cause unintended settings changes for logging settings and other admin settings.
• Attempting to load an (unsupported) tar.gz image results in a poor error message.
• 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 interface. As a workaround use <node-name>/<network-name>.

Version 2.2.14

2018-10-25

Bug fixes

• Core
  • Resolved an issue where LDAP sync jobs terminated when processing an org admin search result that did 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)
• Web Interface
  • Fixed an issue that prevented “Per User Limit” on Admin Settings from working. (docker/escalation#639)

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 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.
• Upgrading heterogeneous swarms from CLI may fail because x86 images are used instead of the correct image for the worker architecture.
• Agent container log is empty even though it’s running correctly.
• Rapid UI settings updates may cause unintended settings changes for logging settings and other admin settings.
• Attempting to load an (unsupported) tar.gz image results in a poor error message.
• 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 interface. As a workaround use <node-name>/<network-name>.

Version 2.2.13

2018-08-30

Bug fixes

• Security
  • Fixed a critical security issue to prevent UCP from accepting certificates from the system pool when adding client CAs to the server that requires mutual authentication.

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 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.
• Upgrading heterogeneous swarms from CLI may fail because x86 images are used instead of the correct image for the worker architecture.
• Agent container log is empty even though it’s running correctly.
• Rapid UI settings updates may cause unintended settings changes for logging settings and other admin settings.
• Attempting to load an (unsupported) tar.gz image results in a poor error message.
• 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 interface. As a workaround use <node-name>/<network-name>.

Version 2.2.12

2018-08-09

Bug fixes

• Security
  • Fixed a critical security issue where the LDAP bind username and password were stored in cleartext on UCP hosts. Please refer to the following KB article https://success.docker.com/article/upgrading-to-ucp-2-2-12-ucp-3-0-4/ for proper implementation of this fix.

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 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.
• Upgrading heterogeneous swarms from CLI may fail because x86 images are used instead of the correct image for the worker architecture.
• Agent container log is empty even though it’s running correctly.
• Rapid UI settings updates may cause unintended settings changes for logging settings and other admin settings.
• Attempting to load an (unsupported) tar.gz image results in a poor error message.
• 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 interface. As a workaround use <node-name>/<network-name>.

Version 2.2.11

2018-07-26

New platforms

• UCP 2.2.11 is supported running on RHEL 7.5 and Ubuntu 18.04.

Bug fixes

• Security
  • Fixed an issue that causes some security headers to not be added to all API responses.
• Core
  • Optimized swarm service read API calls through UCP.
  • Upgraded RethinkDB image to address potential security vulnerabilities.
  • Fixee an issue where removing a worker node from the cluster would cause an etcd member to be removed on a manager node.
  • Upgraded etcd version to 2.3.8.
  • Fixed an issue that causes classic Swarm to provide outdated data.
  • Fixed an issue that raises ucp-kv collection error with unnamed volumes.
• 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.

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 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.
• Upgrading heterogeneous swarms from CLI may fail because x86 images are used instead of the correct image for the worker architecture.
• Agent container log is empty even though it’s running correctly.
• Rapid UI settings updates may cause unintended settings changes for logging settings and other admin settings.
• Attempting to load an (unsupported) tar.gz image results in a poor error message.
• 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 interface. As a workaround use <node-name>/<network-name>.

Version 2.2.10

2018-05-17

Bug fixes

• Security
  • Security headers are added for PCI compliance to all API responses.
• 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 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.
• Authentication/Authorization
  • Private collections are now only created for those users which have previously logged in.
  • The logic which reconciles collection labels is now skipped if the node already has an access label.
  • Fixed an issue where LDAP syncs would always search against the last server in the list of additional domains if the search base DN matched any of those domains.
• Core
  • UCP can now be displayed in an iframe for pages hosted on the same domain.
  • Fixed an issue that prevents non-admin users to do docker build on UCP.
  • Fixed an issue where a node’s status may be reported incorrectly in node listings.
  • UCP can now be installed on a system with more than 127 logical CPU cores.
  • Improved the performance of UCP’s local and global health checks.

Known issues

• Excessive delay is seen when sending docker service ls through a UCP client bundle on a cluster that is running thousands of services.
• 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 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.
• Upgrading heterogeneous swarms from CLI may fail because x86 images are used instead of the correct image for the worker architecture.
• Agent container log is empty even though it’s running correctly.
• Rapid UI settings updates may cause unintended settings changes for logging settings and other admin settings.
• Attempting to load an (unsupported) tar.gz image results in a poor error message.
• 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 interface. As a workaround use <node-name>/<network-name>.

Version 2.2.9

2018-04-17

Bug fixes

• Security
  • Fixed an issue that allows users to incorrectly interact with local volumes.
  • Fixed an issue where setting minimum TLS version causes ucp-agent to keep restarting on worker nodes.
• Core
  • Fixed an issue that causes container fail to start with container ID not found during high concurrent API calls to create and start containers.

Known issues

• RethinkDB can only run with up to 127 CPU cores.
• When integrating with LDAP and using multiple domain servers, if the default server configuration is not chosen, then the last server configuration is always used, regardless of which one is actually the best match.
• 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 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.
• Upgrading heterogeneous swarms from CLI may fail because x86 images are used instead of the correct image for the worker architecture.
• Agent container log is empty even though it’s running correctly.
• Rapid UI settings updates may cause unintended settings changes for logging settings and other admin settings.
• Attempting to load an (unsupported) tar.gz image results in a poor error message.
• 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 interface. As a workaround use <node-name>/<network-name>.

Version 2.2.7

2018-03-26

Bug fixes

• Fixed an issue where the minimum TLS version setting is not correctly handled, leading to non-default values causing ucp-controller and ucp-agent to keep restarting.

Known issues

• RethinkDB can only run with up to 127 CPU cores.
• When integrating with LDAP and using multiple domain servers, if the default server configuration is not chosen, then the last server configuration is always used, regardless of which one is actually the best match.
• 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 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.
• Upgrading heterogeneous swarms from CLI may fail because x86 images are used instead of the correct image for the worker architecture.
• Agent container log is empty even though it’s running correctly.
• Rapid UI settings updates may cause unintended settings changes for logging settings and other admin settings.
• Attempting to load an (unsupported) tar.gz image results in a poor error message.
• 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 interface. As a workaround use <node-name>/<network-name>.

Version 2.2.6

2018-03-19

New features

• Security
  • 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.
  • Added more information to the telemetry data: kernel version, graph driver, and logging driver.
  • The dsinfo image used for support dumps is now smaller.

Bug fixes

• Core
  • The HRM service is no longer deployed with constraints that might prevent the service from ever getting scheduled.
  • Fixed a problem causing the HRM service to be restarted multiple times.
  • The ucp-agent service is now deployed without adding extra collection labels. This doesn’t change the behavior of the service.
  • Fixed problem causing a healthy ucp-auth-store component to be reported as unhealthy.
  • Fixed a race condition causing the labels for the UCP controller container to be reset.
  • Fixed an issue causing the ucp-agent service to be deployed with the wrong architecture on Windows nodes.
• RBAC
  • Role-based access control can now be enforced for third-party volume plugins, fixing a known issue from UCP 2.2.5.
  • Admins can now clean up volumes and networks that had inconsistent collection labels across different nodes in the cluster. Previously, they would have had to go onto each node and clean up those resources directly.
  • When upgrading from UCP 2.1, inactive user accounts are no longer migrated to the new RBAC model.
  • Fixed an issue preventing users from seeing a collection when they have permissions to deploy services on a child collection.
  • Grants are now deleted when deleting an organization whose teams have grants.
• UI
  • Fixed a problem in the Settings page that would cause Docker to stop when you made changes to UCP settings and a new manager node is promoted to leader.
  • Fixed bug causing the Grants list page not to render after deleting an organization mentioned used on a grant.
  • Fixed a problem that would intermittently cause settings not to be persisted.
  • Fixed an issue that prevented users from being able to change LDAP settings.

Known issues

• RethinkDB can only run with up to 127 CPU cores.
• When integrating with LDAP and using multiple domain servers, if the default server configuration is not chosen, then the last server configuration is always used, regardless of which one is actually the best match.
• 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 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.
• Upgrading heterogeneous swarms from CLI may fail because x86 images are used instead of the correct image for the worker architecture.
• Agent container log is empty even though it’s running correctly.
• Rapid UI settings updates may cause unintended settings changes for logging settings and other admin settings.
• Attempting to load an (unsupported) tar.gz image results in a poor error message.
• 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 interface. As a workaround use <node-name>/<network-name>.

Version 2.2.5

2018-01-16

Bug fixes

• Role-based access control is now enforced for volumes managed by third-party volume plugins. This is a critical security fix for customers that use third-party volume drivers and rely on Docker Universal Control Plane for tenant isolation of workloads and data. Caution is advised when applying this update because users or automated workflows may have come to rely on lack of access control enforcement when manipulating volumes created with 3rd party volume plugins.

Known issues

• UCP role-based access control is not compatible with all third-party volume plugins. If you’re using certain third-party volume plugins (such as Netapp) and are planning on upgrading UCP, you can skip 2.2.5 and wait for the upcoming 2.2.6 release, which will provide an alternative way to turn on RBAC enforcement for volumes.
• 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 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.
• Upgrading heterogeneous swarms from CLI may fail because x86 images are used instead of the correct image for the worker architecture.
• Agent container log is empty even though it’s running correctly.
• Rapid UI settings updates may cause unintended settings changes for logging settings and other admin settings.
• Attempting to load an (unsupported) tar.gz image results in a poor error message.
• 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 interface. As a workaround use <node-name>/<network-name>.

Version 2.2.4

2017-11-02

News

• Docker Universal Control Plane now supports running managers on IBM Z on RHEL, SLES and Ubuntu. Previously, only workers were supported on IBM Z.

Bug fixes

• Core
  • ucp-etcd system images are now hidden. Previously, these system images were erroneously displayed in the images list.
  • disable_usageinfo will now disable usage metrics. A regression caused this setting to not be respected.
  • UCP now outputs “Initializing...” log messages during setup so that administrators can establish that setup or install has begun.
  • Windows worker promotion is now blocked. Previously, Windows workers could be promoted using the CLI, which would fail.
  • Loading gzipped images with the Docker CLI is now supported. This would previously cause a panic.
  • Permissions are now checked when filtering nodes by container. Previously, permissions were not considered.
  • An LDAP sync is now triggered as soon as an LDAP user is lazy-provisioned. Previously, lazy-provisioned users would not immediately be added to teams and orgs.
• UI/UX
  • License page now shows all capabilities. Previously it was not clear if a license supported Docker image scanning or not.
  • 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 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 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.
• Upgrading heterogeneous swarms from CLI may fail because x86 images are used instead of the correct image for the worker architecture.
• Agent container log is empty even though it’s running correctly.
• Rapid UI settings updates may cause unintended settings changes for logging settings and other admin settings.
• Attempting to load an (unsupported) tar.gz image results in a poor error message.
• 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 interface. As a workaround use <node-name>/<network-name>.

Version 2.2.3

2017-09-13

Bug fixes

• Core
  • Node list will no longer show duplicated worker node entries.
  • Volume mount options are no longer dropped when creating volumes.
  • docker stack deploy with secrets specified in docker-compose file now works.
• UI/UX
  • Upgrade button is now greyed out and deacticated after initiating upgrade.
  • If an error is encountered while creating a service, the UI no longer freezes.
  • Upgrade notification fixed to have working link.
  • “Default Role For All Private Collections” can now be updated. Updating this role in the UI previously had no effect.
  • Added notification to UI to show that an upgrade is in progress.
  • Client bundle can now be downloaded with Safari browser.
  • Windows nodes are no longer displayed in the DTR install UI.
  • DTR settings state in UCP is now preserved when switching tabs. Previously, un-saved state was lost when switching tabs.
  • Fixed problem where first manager node may have IP address 0.0.0.0, causing dashboard to not update.
  • UI for adding Windows nodes improved to include full join instructions.
  • Node Task UI fixed. Displaying tasks for a node previously did not work.
  • LDAP settings UI improved. Sync interval setting is now validated, a never-ending update spinner been fixed and it’s UI action sequencing bugs have been fixed so that it’s now possible to disable LDAP.
  • Uploading Docker images in the UI now has better error messages and improved validation.
  • Containers removed in UI are now force-removed. Previously removing containers would fail.
  • DTR install instructions --ucp-url parameter fixed to have valid value.
  • Deleting multiple users in succession fixed. Previously, an error would result when deleting more than one user at a time.
  • Added validation when adding DTR URL in UCP admin settings.
  • Left-nav now shows resource counts, addressing an UI regression from UCP 2.1.

Known issues

• Upgrading heterogeneous swarms from CLI may fail because x86 images are used instead of the correct image for the worker architecture.
• Agent container log is empty even though it’s running correctly.
• Rapid UI settings updates may cause unintended settings changes for logging settings and other admin settings.
• Attempting to load an (unsupported) tar.gz image results in a poor error message.
• 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 interface. As a workaround use <node-name>/<network-name>.

version 2.2.2

2017-08-30

Bug fixes

• Core
  • Fixed an issue that caused timeouts during install, preventing UCP 2.2.1 from being released.
  • Fixed a number of issues in which access control labels and roles could not be upgraded to their new format, when upgrading UCP. Learn more.
  • Fixed an issue that caused an upgrade with multiple manager nodes to fail with RethinkDB startup errors.
  • Fixed an issue that caused upgrades to fail due to UCP being unable to remove and replace older UCP containers.
  • Fixed an issue in which upgrade timed out due to lack of available disk space.
  • Fixed an issue in which rescheduling of containers not belonging in services could fail due to a request for a duplicate IP address.
  • DTR containers are no longer omitted from docker ps commands.
• UI/UX
  • Fixed known issue from 2.2.0 where config changes (including LDAP/AD) take an extended period to update after making changes in the UI settings.
  • Fixed an issue where the /apidocs url redirected to the login page.
  • Fixed an issue in which the UI does not redirect to a bad URL immediately after an upgrade.
  • Config and API docs now show the correct LDAP sync cron schedule format.
• docker/ucp image
  • Support dump now contains information about access control migrations.
  • The ucp-auth-store and ucp-auth-api containers now report health checks.

Known issues

• UI issues:
  • 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 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 interface doesn’t apply the HRM labels to the network. As a workaround, create the network using the CLI.
  • 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.
• 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 interface.
• Compose
  • When deploying compose files that use secrets, the secret definition must include external: true, otherwise the deployment fails with the error. unable to inspect secret.
• 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 network prior to attaching Windows services.

Version 2.2.0

2017-08-16

New features

• The role-based access control system has been overhauled for additional granularity and customization. Admins now define access control through Grants, a 1:1:1 mapping of a Subject, a Role, and a Collection:
  • Subject: A user, team, or organization.
  • 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 (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 for more information and examples of the new system and how your old access control settings are migrated during an upgrade.
• UCP now provides access control for nodes, where an admin can enforce physical isolation between users on different nodes in the cluster. This means two different teams can only view and deploy on the nodes to which they have access. This is only available with an EE Advanced license.
• Enhancements to the user management system:
  • UCP now supports the user concept of organizations, which are groups of teams.
  • Users can now specify a default collection which automatically applies access control labels to all CLI deploy commands when no label is specified by the user.
• Support for UCP workers running Windows Server 2016, and the ability to deploy Windows-based containerized applications on the cluster.
  • Read the documentation for instructions on how to join Windows nodes, and current limitations when deploying Windows applications.
• 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 web interface.
• Support for using services with macvlan networks and configuring network scope in UI.
• 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.
  • Filtering mechanism to display related items (e.g. resources in a collection or stack).

Known issues

• UI issues:
  • 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 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 interface doesn’t apply the HRM labels to the network. As a workaround, create the network using the CLI.
  • 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.
• 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 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 network prior to attaching Windows services.

Release notes for earlier versions

• UCP 2.1 release notes
• UCP 2.0 release notes
• UCP 1.1 release notes