Operate
Add and manage cluster nodes
Prepare an installation for additional nodes, approve their identities, and check service readiness.
Before you start
Begin with a working Primary and a usable registration allowance or active term. Prepare private connectivity, matching builds, the chosen database provider, and shared storage.
A single server does not need an active private cluster listener. Internal node certificates are separate from browser facing HTTPS certificates.
Add a node
- Open Registration & licence on the Primary and choose Prepare for additional nodes.
- Configure the private cluster address and port shown by the Product. Allow that port only between intended nodes.
- Install the matching RC1 Node package on the other machine and select its services.
- Follow the node enrolment instructions to submit its join request to the installation.
- On the current authority, review the requested identity and services before approving the join.
- Wait for the Node to receive its approved configuration and become ready.
- Review trusted nodes and any required signed node inventory update.
Check the result
Confirm the Node is approved, reporting, and ready for each selected service. Reachability alone does not prove membership, licence admission, shared storage access, or model readiness.
The installation can run more than one Workflow or AI server. Work ownership and service routing still depend on the current ready node set.
Manage authority and service changes
Use the current configuration authority for shared settings and registration. Review the target readiness before a supported authority transfer. Authority transfer retains the installation allowance.
Service switch off requires another approved and ready process for the same role. Active work can be interrupted. Check saved jobs and recovery after a controlled reload.
If a node cannot connect
Check the displayed destination, private port, firewall, current certificate, node approval, and build. Do not expose the private listener publicly or bypass certificate checks.
Remove or recover a node
Revoke a Node before uninstalling it. Remove Nodes before the Primary. Use the recorded recovery path for a permanently lost node. Do not erase membership history or protected identity files.
After registration allowance expiry, general node administration is unavailable. Restore registration before unrelated cluster changes.
Next step
Was this page helpful?
Your answer helps us improve the documentation.
Do not include personal information, customer information, passwords, or keys.