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

ci: adjust storage requests #3699

Merged
merged 1 commit into from
Jan 29, 2024
Merged

ci: adjust storage requests #3699

merged 1 commit into from
Jan 29, 2024

Conversation

conorsch
Copy link
Contributor

Makes two changes to the PVCs:

  • preview 50G -> 20G
  • testnet 200G -> 300G

We don't need 50GB of storage per node on preview. That's >2 weeks runtime, and we've never gone >2 weeks without deploying to preview. For testnet, though, we grow the storage requests: 200GB is roughly ten weeks, and we're approaching full utilization on Testnet 64 already.

We can still adjust these storage requests over time, but updating them now to reflect our expectations.

Makes two changes to the PVCs:

  * preview 50G -> 20G
  * testnet 200G -> 300G

We don't need 50GB of storage per node on preview. That's >2 weeks
runtime, and we've never gone >2 weeks without deploying to preview.
For testnet, though, we grow the storage requests: 200GB is roughly ten
weeks, and we're approaching full utilization on Testnet 64 already.

We can still adjust these storage requests over time, but updating them
now to reflect our expectations.
@conorsch conorsch merged commit 5ea633f into main Jan 29, 2024
7 checks passed
@conorsch conorsch deleted the rework-persistence-sizes branch January 29, 2024 23:43
conorsch added a commit that referenced this pull request Feb 7, 2024
Follow-up to #3699, which introduced a YAML typo I overlooked.
Will need to be backported to release branch for 65 if we want to use
the automated deploy pipeline.
conorsch added a commit that referenced this pull request Feb 8, 2024
Follow-up to #3699, which introduced a YAML typo I overlooked.
Will need to be backported to release branch for 65 if we want to use
the automated deploy pipeline.
conorsch added a commit that referenced this pull request Feb 8, 2024
Follow-up to #3699, which introduced a YAML typo I overlooked.
Will need to be backported to release branch for 65 if we want to use
the automated deploy pipeline.
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

Successfully merging this pull request may close these issues.

1 participant