From fe8a830dc708f8d6021fe1be9bb68bfa7ebdaa0f Mon Sep 17 00:00:00 2001 From: ddeyo Date: Thu, 1 Nov 2018 14:47:11 -0700 Subject: [PATCH] engine upgrade known issue added --- 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 d858c6e9e4..58dee7a06c 100644 --- a/ee/ucp/release-notes.md +++ b/ee/ucp/release-notes.md @@ -75,6 +75,8 @@ There are several backward-incompatible changes in the Kubernetes API that may a * 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](https://github.com/kubernetes/kubernetes/pull/61373). 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](../upgrade) + * 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: