You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 19, 2022. It is now read-only.
When cakeshop is included in an K8s/Quorum qubernetes network, the nodes in the network should be automatically added to cakeshop at startup. Currently, the nodes have to be manually added when the network starts up.
Additionally when new nodes are added to the network, they could be added to cakeshop. This could be done by either:
Modifying the initial node config and redeploying cakeshop so that it picks up the changes (K8s will automatically do this is the deployment file changes and kubectl apply out as it is when new nodes are added).
Have cakeshop read off a file, nodeconfig and keep this in sync (pull ever X seconds), which would be the source of truth for the nodes that cakeshop should display (similar to permissioned-nodes.json in geth).
When cakeshop is included in an K8s/Quorum qubernetes network, the nodes in the network should be automatically added to cakeshop at startup. Currently, the nodes have to be manually added when the network starts up.
Additionally when new nodes are added to the network, they could be added to cakeshop. This could be done by either:
Modifying the initial node config and redeploying cakeshop so that it picks up the changes (K8s will automatically do this is the deployment file changes and
kubectl apply out
as it is when new nodes are added).Have cakeshop read off a file, nodeconfig and keep this in sync (pull ever X seconds), which would be the source of truth for the nodes that cakeshop should display (similar to
permissioned-nodes.json
in geth).Update via the API.
see:
https://github.com/ConsenSys/qubernetes/blob/master/examples/config/cakeshop.yaml
https://github.com/ConsenSys/qubernetes/blob/master/templates/k8s/cakeshop.yaml.erb
The text was updated successfully, but these errors were encountered: