Does the vault agent mode support cloud auto join like in consul auto join method?
basically, because we have consul cluster (server and client) that depend on vault to get the gossip, tls, etc from the vault,
I our case so we can’t use the consul dns for service discovery, and we didn’t want to add domain / load balancer in front of vault,
so the option in our mind is to use cloud auto join, does vault agent support this options?
I wouldn’t recommend it, as I think it would be too fragile, but it’s technically possible.
I don’t think Vault agent supports live updates to the Vault URL though… In which case you would need to restart it… Which would cause more issues. It doesn’t seem like a promising direction to me.
Use either a load-balancer or a DNS-based service discovery system (such as Consul - perhaps second tiny deployment with no runtime dependency on Vault), to provide a URL at which Vault can be reached without hard-coding the address of a specific Vault node into the Vault agent configuration.
That’s a bad idea, you’re making a single instance the fault point and basically undoing any HA that a simple cluster gives you. Why don’t you want to add a load balancer?
@aram we didn’t want to have footprint of our vault server address in DNS, especially for a threat actor… as we can’t do whitelisting because we want our client node (nomad + consul + vault client) to connect it with public network.
@petrukngantuk1 I’m not sure who came up with those as remedies but I’m sorry to say they make absolutely no sense whatsoever. I’m lost for words. I would highly suggest you seek a consultant to help you mitigate your decisions as you’re just setting yourself up for a major breach and disaster.