From 02ab1ec89151222c8203dbf7655ed8c29cb8a270 Mon Sep 17 00:00:00 2001 From: ddeyo Date: Fri, 2 Nov 2018 11:38:02 -0700 Subject: [PATCH] LDAP disappearing settins added to known issues --- ee/ucp/release-notes.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/ee/ucp/release-notes.md b/ee/ucp/release-notes.md index 58dee7a06c..12c2d61770 100644 --- a/ee/ucp/release-notes.md +++ b/ee/ucp/release-notes.md @@ -77,6 +77,8 @@ There are several backward-incompatible changes in the Kubernetes API that may a ## 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](../upgrade) +* In the UCP web interface, LDAP settings disappear after submitting them. However, the sattings 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: