-
Notifications
You must be signed in to change notification settings - Fork 7
✨ Automatic cluster formation using DNS #689
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
base: main
Are you sure you want to change the base?
Conversation
|
|
Robot Results
Passed Tests
Failed Tests
|
Hi @atpugtihsrah ! I take the opportunity of this new PR to mention, I created a Discord server for the community ( invite link #686 ) to be able to help if people have troubles when contributing :) |
@linkdd Awesome, I just joined! |
f1addab
to
424f531
Compare
424f531
to
8c47fda
Compare
|
Hi @atpugtihsrah, I hope you're doing well. I am starting work on the Kubernetes automatic cluster formation. To do so, I decided to simplify the way we add a new strategy for cluster formation, you can find the PR here #788. This will impact your PR, but I hope it will simplify your work. Let me know what you think and have a good day :) |
Hey @linkdd Thanks for the heads up. I am slowly making progress, dns has a learning curve (and that's why I picked this task). I have a lot of changes on my machine which I don't want to commit right now because I don't know if those changes work or not. As soon as I make a commit I will check your PR, pull in your changes and rebase. |
Signed-off-by: Harshit Gupta <[email protected]>
bad7761
to
423c06f
Compare
|
Decision Record
Why: DNS can also be used for service discovery. So we want to also offer service discovery using DNS for FlowG.
Closes ✨ Automatic cluster formation using DNS discovery #424
Changes
Task List:
License Agreement