ObolNetwork / ObolNetwork/obol-stack
[Idea] Expose the Nethermind EL UI in `mode=full`
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 11
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
Problem to be solved
We want to monitor the health of the obol stack full node when installed. That may be
Proposed solution
(when mode != headless i.e. we're running the stack with an ingress)
(when mode = full. and we still only pick nethermind as a CL)
Enable the UI on the nethermind client by passing the appropriate flag added to ethereum-node chart.
Add an ingress manifest file to ~/.local/obol/manifests/expose-nethermind.yaml or similar, (or add it to the L1 applyset) that exposes the nethermind el UI on http://obol.stack/l1/el.
On the obol front end, add a view Dashboard button to the nethermind component, that opens http://obol.stack/l1/el in a new tab, when clicked. This allows a stack user to open the nethermind dashboard and view it.
Contributor guide
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.
Research direction
Start by locating the ethereum-node chart, the Obol front end's Nethermind component, and the L1 applyset or ~/.local/obol/manifests area. Check how ingress is handled for mode=full versus headless. Done means the Nethermind EL UI is exposed at http://obol.stack/l1/el in full mode and the component has a working Dashboard link that opens it in a new tab.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, helm, kubernetes
- Domain
- devops, frontend, infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100