search

hashicorp / boundary

Boundary enables identity-based access management for dynamic infrastructure.
https://boundaryproject.io
Other
3.85k stars 288 forks source link

Support SRV records lookups for Boundary Hosts #1811

Open oboukili opened 2 years ago

oboukili commented 2 years ago

Some targets may benefit from DNS SRV discovery, for example headless Kubernetes services, or any SaaS vendor regularly updating the topology of their exposed headless endpoints.

The Boundary host object should support an additional attribute (address_srv ) which points at a SRV record. Before establishing the worker' tcp connection to the target, the worker should execute a DNS SRV lookup and (randomly?) choose one of the returned responses.

jefferai commented 2 years ago

Our preferred/eventual approach for Kubernetes would be to integrate directly with the service catalog, in a fashion similar to the dynamic host catalogs for AWS/Azure that came out in 0.7. Would that work for your needs?

What SaaS vendors have changing headless endpoints that require SRV lookups as opposed to A records?

oboukili commented 2 years ago

On the top of my head, I can think of MongoDB atlas.

jboero commented 1 year ago

@hashicorp/boundary any roadmap for this feature? Getting multiple bumps from partners in EMEA. Thanks

tylersmith34 commented 7 months ago

MongoDB Atlas still uses this method for private link connected clusters. I just had to pull the plug when I learned Boundary doesn't support this and open up the private links my the entire corporate network. That's the last thing I wanted to do and is what Boundary let's me prevent for our other databases.

Please, please, please support this!