DNS resolution for dynamic nodes
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 20/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- go, kubernetes
- Domain
- infrastructure, networking
Research direction
No files, tests, or entry points are named in the issue. Begin by locating where DNS is resolved at startup and clarifying the runtime-refresh constraints for nodes scaled by Kubernetes; done requires an agreed approach and acceptance criteria before implementation.
Written by the indexing model from the issue text.
Description
Hey 👋
Quick question, why the DNS is resolved at startup only? Why we can’t rely in runtime resolution?
Here we are running nodes on k8s that are constantly getting scaled up and down so a more robust solution is needed. What is a preferred method of refreshing DNS? I could work on a PR for it, but important to understand the constraints and the context first.
Thanks!
- Dominant language
- Go
- Stars
- 4
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from flashbots/bproxy
-
enhancement
Difficulty 3/5 1-2 days Newbie friendliness 45/100
-
enhancement
Difficulty 4/5 3-5 days Newbie friendliness 45/100
All issues in flashbots/bproxy
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
bug group: validation priority: low
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
codecheckers/chekhov#51 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100