I have a good concept of how satellites and agents work manually, but I’m having some trouble figuring this out with Director. I’m trying to keep the configuration mainly confined to Director as I’m using Kubernetes and the container images, and it’s not quite as easy to do a bunch of custom manual configuration with this setup. The documentation seems more or less silent on this.
To start, I got a host added with agent installed and can easily get service checks running on that host as the check source. What I want to do is configure this host now as a satellite where I can configure other hosts and have the service checks run on the agent/satellite. There is no inward communication from my master instance to the network where the agent/satellite is installed.
I’ve tried adding a zone manually, but that seems to break the checks and configuration when I assign the host to that new zone. I haven’t updated or added the endpoint configuration. I can see that Director added both a zone and endpoint for the agent in the deployed configuration, they just aren’t visible in Director directly.
Ultimately, what are the steps to get this working? Is it possible to do all or most of this in Director?
Stellites can’t be setup in the director ATM but after it’s done manually the config import gets them into the director and from then on they can be used in the director.
I strongly advise against using the Director to configure satellite endpoints and zones.
I our setup (admittedly with many zones) it came apart after some time and we moved all satellite zones to the masters zones.conf file.
For the agents, doing this via a Template with the provided dropdown fields, is fine and works well.
You can control the direction for the communication via the host attribute in the endpoint object.
Setting the attribute in the satellites endpoint object on the master will mean that the master will try to connect to the satellite.
Setting the attribute on the satellite in the masters endpoint object will let the satellite connect to the master (preferred, as it takes a bit of load and log clutter from the master).
The satellite then has to be configured to accept_config and accept_commands in the api feature.
