IAG server requirements

This guide provides server specifications and scaling models for IAG5 distributed deployments.

Server node specifications

In distributed mode, server nodes (controllers) retrieve information from the database and route automation work to runner nodes. Because server nodes don't perform the automation work themselves, you can use smaller, lightweight instances.

You typically need only two server nodes to create a highly available cluster. Scaling beyond two nodes isn't usually necessary.

Server nodes handle these tasks:

• Retrieve repository information, encrypted secrets, and other data from the database when you execute a service
• Create and delete IAG resources (services, repositories, decorators)

Server node requirements

Runner node specifications

Runner nodes execute the automation work in both distributed mode and all-in-one mode. These instances need more processing power than server nodes. You can scale runner nodes horizontally as your workload increases by adding nodes with the appropriate configuration to the cluster. Remove nodes when workloads decrease.

Runner node requirements

Etcd specifications

When you run IAG5 in distributed mode, you can use etcd as the backing persistence store. Configure etcd in a highly available cluster with at least three nodes. Don't install etcd nodes on the same physical nodes as your servers and runners. For etcd nodes, memory is the most important consideration.

For more information about etcd, see the etcd website.

Etcd node requirements