Skip to main content

​
Consul role in the cluster

Both cluster-n03 and cluster-n04 run Consul server agents. These form part of the wider Consul server cluster used for:
  • Service discovery
  • Configuration / key-value storage
  • Integrations with tools like Traefik

​
Consul on cluster-n03

  • Service: consul.service (enabled, active)
  • Binary / mode (from systemd command):
    • /home/consul/consul agent -server
    • -config-dir=/home/consul/consul-config/
    • -data-dir=/home/consul/consul-data/
    • -node=node03.cluster.devops.arabiaweather.com
    • -bind=94.130.9.47
There is no /etc/consul.d directory; configuration is kept under /home/consul/consul-config/.

​
Consul on cluster-n04

  • Service: consul.service (enabled, active)
  • Binary / mode:
    • /home/consul/consul agent -server
    • -config-dir=/home/consul/consul-config/
    • -data-dir=/home/consul/consul-data/
    • -node=node04.cluster.devops.arabiaweather.com
    • -bind=94.130.88.29
Same layout as cluster-n03, with node/bind addresses adjusted.

​
Traefik

On both nodes:
  • No local Traefik binary is installed (traefik and /usr/local/bin/traefik are missing).
  • There is no /etc/traefik configuration directory.
That means Traefik instances live elsewhere (e.g. on edge nodes or another cluster) and use this Consul cluster as a control plane, reading service definitions and configuration from Consul.

​
Useful commands

ssh cluster-n03
systemctl status consul

ssh cluster-n04
systemctl status consul
For more detailed Consul behavior, consult the central Consul / Traefik documentation and configuration repositories.