Adding and removing nodes¶
You can view, add, edit and delete server nodes from Anaconda Enterprise using the Admin Console’s Operations Center. If you would prefer to use a command line to join additional nodes to the AE master, follow the instructions provided below.
- Each installation can only support a single AE master node, as this node includes storage for the platform. DO NOT add an additional AE master node to your installation.
- As a best practice for etcd optimal cluster size, we recommend you add any additional Kubernetes master nodes in pairs, so that the total number (including the AE master) is an odd number.
- Anaconda Enterprise doesn’t support running heterogeneous versions in the same cluster. Before adding a new node, verify that the node is operating the same version of the OS as the rest of the cluster.
- If you’re adding a GPU node, make sure it meets the GPU requirements.
To manage the servers on your system:
- Log in to Anaconda Enterprise, select the Menu icon in the top
right corner and click the Administrative Console link displayed at the
bottom of the slide out window. You must be logged in with a user assigned to
- Click Manage Resources.
- Log in to the Operations Center using the Administrator credentials configured after installation.
- Select Nodes from the menu on the left to display the configured nodes in your cluster, their IP address, hostname and profile.
To add an existing server to Anaconda Enterprise:
- Click the Add Node button at the top right.
Select an appropriate profile for the server and click Continue.
Copy and paste the command provided into a terminal window to add the server.
When you refresh the page, your server will appear in the list.
To remove a server node:
and select Delete….
To log on to a server:
and select root to open a terminal window. It will open a new tab in your browser.
Using the command line to add nodes¶
Download the gravity binary that corresponds to your version of Anaconda Enterprise from the S3 location provided to you by Anaconda onto the server you’re adding to the cluster.
Rename the file to something simpler, then make it executable. For example:
mv gravity-binary-6.1.9 gravity chmod +x gravity
On the AE master, run the following command to obtain the join token and IP address for the AE master node:
The results should look similar to the following:
Copy and paste the join token for the cluster and the IP address for the AE master somewhere accessible. You’ll need to provide this information when you add a new worker node. You’ll also need the IP address of the server node you’re adding.
On the worker node, run the following command to add the node to the cluster:
./gravity join --token JOIN-TOKEN --advertise-addr=NODE-IP --role=NODE-ROLE --cloud-provider=CLOUD-PROVIDER MASTER-IP-ADDR
JOIN-TOKEN = The join token that you obtained in Step 3.
NODE-IP = The IP address of the worker node. This can be a private IP address, as long as the network it’s on can access the AE master.
NODE-ROLE = The type of node you’re adding:
CLOUD-PROVIDER = This is auto-detected, and can therefore be excluded unless you don’t have Internet access. In this case, use
MASTER-IP-ADDR = The IP address of the AE master that you obtained in Step 3.
--role flag must be provided and assigned to either
k8s-master. Without it the node will be added
with the role
ae-master and may cause your cluster to crash.
The progress of the join operation is displayed:
- To monitor the impact of the join operation on the cluster, run the
gravity statuscommand on the AE master.
The output will look similar to the following:
Note that the size of the cluster is
expanding and the status of the new node being added is
offline. When the node has successfully joined, the cluster returns to an
active state, and the status of the new node changes to