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

Merge branch 'master' of https://github.com/docker/docs-private into landing-pages

This commit is contained in:
Dawn W Docker 2019-12-13 14:07:06 -08:00
parent 890ce00b5c 15f4c78350
commit 35b6f11163
2 changed files with 27 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

21
ee/ucp/admin/configure/join-nodes/join-linux-nodes-to-cluster.md
View File

@ -99,9 +99,8 @@ To promote or demote a manager node:
4. Click **Save** and wait until the operation completes.
5. Navigate to the **Nodes** page, and confirm that the node role has changed.
If you're load-balancing user requests to Docker Enterprise across multiple manager
nodes, don't forget to remove these nodes from your load-balancing pool when
you demote them to workers.
If you are load balancing user requests to Docker Enterprise across multiple manager nodes, remember to remove these nodes from the load-balancing pool when demoting them to workers.
## Remove a node from the cluster
@ -120,10 +119,9 @@ be careful when removing one from the cluster.
To remove a manager node:
1. Make sure all nodes in the cluster are healthy. Don't remove manager nodes
if that's not the case.
2. Demote the manager node into a worker.
3. Now you can remove that node from the cluster.
1. Confirm that all nodes in the cluster are healthy (otherwise, do not remove manager nodes).
2. Demote the manager nodes into workers.
3. Remove the newly-demoted workers from the cluster.
## Use the CLI to manage your nodes
@ -135,3 +133,12 @@ Once you do that, you can start managing your UCP nodes:
```bash
docker node ls
```
## Use the API to manage your nodes
You can use the API to manage your nodes in the following ways:
- Use the node update API to add the orchestrator label (that is, `com.docker.ucp.orchestrator.kubernetes`):
```bash
/nodes/{id}/update
```
- Use the /api/ucp/config-toml API to change the default orchestrator setting. Refer to [scheduling_configuration table (optional)](https://docs.docker.com/ee/ucp/admin/configure/ucp-configuration-file/#scheduling_configuration-table-optional) for more information.

13
ee/ucp/admin/install/system-requirements.md
View File

@ -123,6 +123,19 @@ Number 4 for IP-in-IP encapsulation.
If you're deploying to AWS or another cloud provider, enable IP-in-IP
traffic for your cloud provider's security group.
## Enable connection tracking on the loopback interface for SLES
Calico's Kubernetes controllers can't reach the Kubernetes API server
unless connection tracking is enabled on the loopback interface. SLES
disables connection tracking by default.
On each node in the cluster:
```
sudo mkdir -p /etc/sysconfig/SuSEfirewall2.d/defaults
echo FW_LO_NOTRACK=no | sudo tee /etc/sysconfig/SuSEfirewall2.d/defaults/99-docker.cfg
sudo SuSEfirewall2 start
```
## Timeout settings
Make sure the networks you're using allow the UCP components enough time