Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Setup GCP cluster with load balancers for the boot node #10539

Closed
alexghr opened this issue Dec 9, 2024 · 2 comments · Fixed by #10632
Closed

Setup GCP cluster with load balancers for the boot node #10539

alexghr opened this issue Dec 9, 2024 · 2 comments · Fixed by #10632
Assignees
@just-mitch

Comments

@alexghr
Copy link
Contributor

alexghr commented Dec 9, 2024 •
edited
Loading

Right now services on public networks use host networking so that they're reachable from the public internet but this is not scalable because k8s could pods around rendering public IP addresses invalid.
@alexghr
Copy link
Contributor Author

alexghr commented Dec 9, 2024

Another issue with network: host - if a pod is moved to a different node, its IP address will change but other pods won't be notified of the new URL. e.g. boot node gets moved to a new VM but the bot will keep trying to access it at the old address.

@just-mitch just-mitch self-assigned this Dec 11, 2024
@just-mitch
Copy link
Collaborator

Will also need for faucet.

Eventually will need DNS for services.

@just-mitch just-mitch linked a pull request Dec 11, 2024 that will close this issue
chore: load balancers for the boot node, longer epochs #10632
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@just-mitch just-mitch

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

chore: load balancers for the boot node, longer epochs AztecProtocol/aztec-packages
2 participants
@alexghr @just-mitch