<< Click to Display Table of Contents >> Navigation:  Technical Guide > Architecture > Agent

 

The DTS Agent serves as the interface between the system and the cluster that runs its main module containers.

It is tasked with the following responsibilities:

•Can interact with Kubernetes as well as Docker-only deployments of DTS.

•Starts and stops containers/pods at the request of the Controller.

 

The system can function without an Agent running, but it will not be able to self-regulate - all producers will need to be started and stopped manually or by other means, and automatic restarting of unresponsive producers will not be possible.

In order to control the cluster, the Agent must run outside of it, generally as a stand-alone application or wrapped in a service. It can function on the same machine as the cluster controller or on a remote one with SSH access.

 

The Agent communicates with other modules as follows:

•Internal Communications Bus (Redis): The ICB is used by the Agent to receive commands from the Controller and report on its status.

•SSH/SCP: SSH is used by the Agent to control the deployment cluster if not running on the same machine.