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
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Multicloud deployment using Terraform and Helm
New Terraform code has been added to place helm deployments onto 2 separate Kubernetes clusters (1 AWS, 1 GCloud). Although Terraform has the ability to set values, this is intentionally not used, to simplify customizations to only exist inside of Helm for simpler portability between cloud and local machine environments.
Anvil node storage increase
Anvil currently fails and is evicted from Kubernetes due to exhausting available disc space. At the moment this happens after a few days of block activity. The new disc value is intended to allow Anvil to run continuously for a period of weeks of environments such as long-lived devnet deployments.
Updated default deployment image
The default image in values.yaml is updated to use the latest master branch build.
This doesn't seem to actually have the clusters "talking"? It seems the result of this would be two independent clusters.
From my understanding of #9838, the result of this terraform should be:
prover node/agents in GCP
everything else running in AWS
all nodes are on the same p2p network, and using the L1 deployed in AWS
@just-mitch you are correct. I wanted to merge the working 2 cluster generic deployment, before modifying it to talk to each other. This modification may be needed only within helm, but I needed the working base before going further.
network-allCI: Deprecated, use ci-full. Runs all CI master checks.
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Change Log
Multicloud deployment using Terraform and Helm
New Terraform code has been added to place helm deployments onto 2 separate Kubernetes clusters (1 AWS, 1 GCloud). Although Terraform has the ability to
set
values, this is intentionally not used, to simplify customizations to only exist inside of Helm for simpler portability between cloud and local machine environments.Anvil node storage increase
Anvil currently fails and is evicted from Kubernetes due to exhausting available disc space. At the moment this happens after a few days of block activity. The new disc value is intended to allow Anvil to run continuously for a period of weeks of environments such as long-lived
devnet
deployments.Updated default deployment image
The default image in
values.yaml
is updated to use the latestmaster
branch build.