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.

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

Multi-node deployment environments (k8s/helm, ci/cd) #481

Closed
Tracked by #479
Voxelot opened this issue Jul 11, 2022 · 0 comments
Closed
Tracked by #479

Multi-node deployment environments (k8s/helm, ci/cd) #481

Voxelot opened this issue Jul 11, 2022 · 0 comments
Assignees

Comments

@Voxelot
Copy link
Member

Voxelot commented Jul 11, 2022

Update our CD environment to support running multiple fuel-core nodes connected to each other via fuel-p2p.

General Requirements:

  • At least two or more nodes deployed in K8S
  • Each node must have a unique ingress URL configuration
  • Nodes must bootstrap via ingress URLs (not using local svc connections). This is to ensure our ingress correctly exposes peering ports as if the nodes were running in separate clouds / clusters Using local svc connections for now since we don't have peer reputation on syncing.
@Voxelot Voxelot assigned Voxelot and unassigned leviathanbeak Jan 9, 2023
Voxelot added a commit that referenced this issue Feb 7, 2023
Refs: #481
#647

---------

Co-authored-by: Green Baneling <XgreenX9999@gmail.com>
Co-authored-by: Brandon Kite <brandonkite92@gmail.com>
@Voxelot Voxelot closed this as completed Feb 20, 2023
crypto523 pushed a commit to crypto523/fuel-core that referenced this issue Oct 7, 2024
Refs: FuelLabs/fuel-core#481
FuelLabs/fuel-core#647

---------

Co-authored-by: Green Baneling <XgreenX9999@gmail.com>
Co-authored-by: Brandon Kite <brandonkite92@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants