Sync published with master (#8619)

* Update install.md

add note: 8 character password minimum length

* Include Ubuntu version in Dockerfile

more recent versions of Ubuntu don't work with the given Dockerfile

* Updated the 3.1.4 release notes to include Centos 7.6 support

* Remove redundant "be"

* Update the "role-based access control" link

On page "https://docs.docker.com/ee/ucp/user-access/", update the hyperlink "role-based access control" to point to "https://docs.docker.com/ee/ucp/authorization/" instead of "https://docs.docker.com/ee/access-control".

* Add UCP user password limitation

* Revert "Updated the UCP 3.1.4 release notes to include Centos 7.6 support"

* Adding emphasis on Static IP requirement (#7276)

* Adding emphasis on Static IP requirement

We had a customer (00056641) who changed IPs like this all at once, and they are in a messy status.    We should make it clear that static IP is absolutely required.  
```***-ucp-0-dw original="10.15.89.6" updated="10.15.89.7" 
***-ucp-1-dw original="10.15.89.5" updated="10.15.89.6" 
***-ucp-2-dw original="10.15.89.7" updated="10.15.89.5" ```

* Link to prod requirement of static IP addresses

* Adding warning about layer7 config (#8617)

* Adding warning about layer7 config

Adding warning about layer7 config not being included in the backup

* Text edit

ee/ucp/admin/backups-and-disaster-recovery.md

@@ -27,10 +27,9 @@ UCP maintains data about:
 This data is persisted on the host running UCP, using named volumes.
 [Learn more about UCP named volumes](../ucp-architecture.md).
 
-UCP won't backup your routing mesh settings. After restoring you need to
-[re-enable the routing mesh](../interlock/deploy/index.md). If you've customized
-your layer 7 routing deployment, you'll need to re-apply those customizations too.
-
+> Warning: UCP will not back up your routing mesh settings. After restoring,
+[reenable the routing mesh](../interlock/deploy/index.md). Additionally, if you've customized
+your Layer 7 routing deployment, reapply your custom settings.
 ## Backup steps
 
 Back up your Docker EE components in the following order:

ee/ucp/admin/install/system-requirements.md

@@ -15,8 +15,8 @@ You can install UCP on-premises or on a cloud provider. Common requirements:
 
 * [Docker EE Engine](/ee/supported-platforms.md) version {{ site.docker_ee_version }}
 * Linux kernel version 3.10 or higher
-* A static IP address
-
+* [A static IP address for each node in the cluster](/ee/ucp/admin/install/plan-installation/#static-ip-addresses)
+ 
 ### Minimum requirements
 
 * 8GB of RAM for manager nodes

ee/ucp/user-access/index.md

@@ -13,7 +13,7 @@ way, from your browser.
 
 
 Docker UCP secures your cluster by using
-[role-based access control](../../access-control/index.md).
+[role-based access control](../authorization/index.md).
 From the browser, administrators can:
 
 * Manage cluster configurations,
@@ -30,4 +30,4 @@ containers, and only when they're granted access by an administrator.
 ## Where to go next
 
 - [Authorization](../authorization.md)
-- [Access UCP from the CLI](cli.md)
+- [Access UCP from the CLI](cli.md)

engine/examples/postgresql_service.md

@@ -21,7 +21,7 @@ suitably secure.
 # example Dockerfile for https://docs.docker.com/engine/examples/postgresql_service/
 #
 
-FROM ubuntu
+FROM ubuntu:16.04
 
 # Add the PostgreSQL PGP key to verify their Debian packages.
 # It should be the same key as https://www.postgresql.org/media/keys/ACCC4CF8.asc

engine/security/trust/content_trust.md

@@ -20,7 +20,7 @@ client-side or runtime verification of the integrity and publisher of specific
 image tags. 
 
 Through DCT, image publishers can sign their images and image consumers can 
-ensure that the images they use are signed. Publishers could be be individuals 
+ensure that the images they use are signed. Publishers could be individuals 
 or organizations manually signing their content or automated software supply 
 chains signing content as part of their release process.
 

reference/ucp/3.1/cli/install.md

@@ -44,7 +44,7 @@ If you are installing on Azure, see [Install UCP on Azure](/ee/ucp/admin/install
 
 | Option                   | Description                                                                                                                                                                                                                               |
 |:-------------------------|:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
-| `--admin-password`       | The UCP administrator password |
+| `--admin-password`       | The UCP administrator password. Must be at least 8 characters. |
 | `--admin-username`       | The UCP administrator username                             |
 | `--binpack`              | Set the Docker Swarm scheduler to binpack mode. Used for backwards compatibility       |
 | `--cloud-provider`       | The cloud provider for the cluster