docker
/
docs
mirror of https://github.com/docker/docs.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Add known issue about Kube networks and upgrading

This commit is contained in:
Jim Galasyn 2018-04-17 10:21:24 -07:00
parent 4041c2a4a3
commit 58621ff23b
1 changed files with 3 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -110,6 +110,9 @@ will be available in future releases.
Route-reflector configurations will be included in a future release. Route-reflector configurations will be included in a future release.
* In some deployments the `kube-dns` component won't be able to resolve external * In some deployments the `kube-dns` component won't be able to resolve external
domain names. [Deploy a ConfigMap to work around this](https://kubernetes.io/docs/tasks/administer-cluster/dns-custom-nameservers/#configure-stub-domain-and-upstream-dns-servers). domain names. [Deploy a ConfigMap to work around this](https://kubernetes.io/docs/tasks/administer-cluster/dns-custom-nameservers/#configure-stub-domain-and-upstream-dns-servers).
* 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 * Management
* If upgrading UCP through the UI, UCP will not check to ensure the manager node * If upgrading UCP through the UI, UCP will not check to ensure the manager node
has the minimum memory required of 4 GB. Upgrading through the CLI does check for has the minimum memory required of 4 GB. Upgrading through the CLI does check for