Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support kubernetes based peer identification #1462

Open
trashhalo opened this issue Dec 18, 2024 · 2 comments
Open

Support kubernetes based peer identification #1462

trashhalo opened this issue Dec 18, 2024 · 2 comments
Labels
type: enhancement New feature or request

Comments

@trashhalo
Copy link

I just wanted to point out that for users running in kubernetes which I assume is a majority, you can use a headless service to identify peers. This would allow you to not have redis and reduce the deployed surface area of the application.

I know this because libcluster the distributed cluster library for elixir uses this. The code can be seen here. https://github.com/bitwalker/libcluster/blob/main/lib/strategy/kubernetes_dns.ex

  1. Create a kubernetes service that targets the pods
  2. Use dns to inspect service this gives you the ips of your peers

Feel free to close if not helpful! just wanted to let you know

@trashhalo trashhalo added the type: enhancement New feature or request label Dec 18, 2024
@trashhalo
Copy link
Author

Documentation for DNS records for headless services. https://github.com/kubernetes/dns/blob/master/docs/specification.md#24---records-for-a-headless-service

@codeboten
Copy link
Contributor

Thanks for the suggestion @trashhalo, it's a great idea, we may implement this in the future

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants