From 0f8586caff9448b1f4971b64eb330196eff64cfb Mon Sep 17 00:00:00 2001 From: Joe Abbey Date: Fri, 5 Oct 2018 15:26:43 -0400 Subject: [PATCH 1/2] Update system-requirements.md --- ee/ucp/admin/install/system-requirements.md | 15 ++++++++++++++- 1 file changed, 14 insertions(+), 1 deletion(-) diff --git a/ee/ucp/admin/install/system-requirements.md b/ee/ucp/admin/install/system-requirements.md index fad8028344..85571758d2 100644 --- a/ee/ucp/admin/install/system-requirements.md +++ b/ee/ucp/admin/install/system-requirements.md @@ -94,7 +94,20 @@ 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 it 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 From 15f4c78350584012c68f3178dca1bd9df1374ce8 Mon Sep 17 00:00:00 2001 From: Traci Morrison <52976526+traci-morrison@users.noreply.github.com> Date: Fri, 13 Dec 2019 13:05:00 -0500 Subject: [PATCH 2/2] Add API information (#10021) --- .../join-nodes/join-linux-nodes-to-cluster.md | 21 ++++++++++++------- 1 file changed, 14 insertions(+), 7 deletions(-) diff --git a/ee/ucp/admin/configure/join-nodes/join-linux-nodes-to-cluster.md b/ee/ucp/admin/configure/join-nodes/join-linux-nodes-to-cluster.md index cd3c5d0837..fe5f356c1d 100644 --- a/ee/ucp/admin/configure/join-nodes/join-linux-nodes-to-cluster.md +++ b/ee/ucp/admin/configure/join-nodes/join-linux-nodes-to-cluster.md @@ -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. \ No newline at end of file