It certainly answers it to an extent, thank you!
I assume, when caddy doesn’t sync the config between multiple instances it won’t able to share a virtual IP natively to load balance between multiple nodes either. So, when using caddy as a load balancer for multiple webservers, I’d still need to put a seperate load balancer in front of the caddy cluster to distribute the load between the diffrerent instances.
This would introduce new challenges, like (as funny as it sounds) “unbalanced” load balancing by the different caddy nodes, since they don’t communicate with each other about which of the instances sends how much traffic to each webserver backend.
To sum it up (and please correct me if I’m wrong!), from what I could gather from the documentation and your comment, Caddy is a great load balancer when used as a single instance and supports clustered backend storage for certificates, so that multiple caddy instances can be utilized to gain maximum availability. But for a setup where a clustered load balancer is necessary for which a VIP is being managed by the load balancers themselves and all nodes are aware of each other, I’d still have to rely on a 3rd party solution.
