Everything else — chain, network, node type, and which client runs each role — is fixed at deploy. To change any of it, delete the node and deploy a new one.
Edit resources
Open the node from Nodes, stay on the Overview tab, and use Edit resources on the Resources panel. The dialog lists one block per role, each labelled with its role, client, and version, so on a multi-process node (Ethereum’s execution + consensus pair, Monad’s three roles) you size each process separately. Per role you can set:
Requests and limits are entered with a unit selector (cores or millicores,
Gi or Mi), and each limit field shows the matching request underneath so you can see what you’re capping.
Save resources stays disabled until something actually differs from the current spec. Saving updates the node’s desired spec, and the executor applies the change on its next reconcile.
Storage is Operator-only, and grows only
The Storage field appears only when the node runs on a Kubernetes Operator executor. On a bare-metal Agent there is no storage field — the node’s data lives in a directory on the host, not in a sized volume, so there is nothing to resize from here. On an Operator the dialog is explicit about the constraint: storage can be increased after launch, but Kubernetes PVCs cannot be shrunk. Plan an increase as a one-way move; to reduce a volume you have to redeploy the node.What saving does not do
- It does not move the node to a different executor — that needs a redeploy.
- It does not change the node’s name or identity.
- It does not keep a versioned history to roll back to. Edit again to change a value back.
Edit connections
Nodes that depend on a parent endpoint or a downstream destination have a Connections tab. It appears for:- L2s that read an Ethereum L1 — Base and Robinhood Chain. The tab holds the L1 connection (execution RPC and beacon): change the URLs it points at, or — for Robinhood Chain — switch between an Existing node, a New node, and External URLs, just as in the deploy wizard’s Connections step. Cancel leaves the saved connection untouched. Observed upstream health — last check time, sync progress, height, and lag — stays on Overview.
- Tron event streaming — turn MongoDB event streaming on or off and edit its streams, filters, and destination. See Tron event streaming. Turning streaming off on save removes the plugin and its stored credentials, but leaves data already written in MongoDB.
nodes:deploy permission as deploying. Members can inspect the tab; editing is gated. A stale URL for a node without connections just shows its Overview instead.
Permissions
Owner and admin can edit resources; members don’t see the action at all. See Roles and permissions.Related
- Deploy a node — where initial resources are set.
- Update a node’s version — the one other in-place change to a running node.
- RPC exposure — change how the node’s RPC is published, any time.
- Node lifecycle — start, stop, restart, delete.