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

chore(charts): celestia versions bump #1699

Merged
merged 2 commits into from
Nov 15, 2024

Conversation

quasystaty1
Copy link
Contributor

@quasystaty1 quasystaty1 commented Oct 21, 2024

Summary

updates celestia-node and celestia-local charts to support the new versions.

Background

Celestia mocha-4 testnet went through an upgrade, nodes should upgrade by nov 7th

Changes

  • celestia-app v2.0.0 -> v2.3.1
  • celestia-node v0.16.0-rc -> v0.18.3-mocha
  • adjusts celestia-node config.toml env variables
  • adds pruner service to configs

Testing

celestia-local tested locally running smoke-tests, celestia-node sync tested locally & against flame.

Breaking Changelist

  • celestia environment variable changes

@quasystaty1 quasystaty1 requested a review from a team as a code owner October 21, 2024 07:34
@github-actions github-actions bot added the cd label Oct 21, 2024
@@ -19,7 +20,7 @@ config:

images:
pullPolicy: IfNotPresent
node: ghcr.io/celestiaorg/celestia-node:v0.16.0-rc0
node: ghcr.io/celestiaorg/celestia-node:v0.18.2-mocha
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do any of these settings only work on mocha? Noting that we will have use a different image for mainnet instances.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Both tags have the same commit on celestia-node:
v0.18.2-mocha
v0.18.2-arabica
I believe celestia tags their networks unrelated to actual code change. Either way changes should work on other networks as well. Correct about mainnet, will most likely run a separate celestia-node instance with the older version.

@quasystaty1 quasystaty1 force-pushed the quasystaty1/charts/upgrade-celestia-node branch from a40d45b to 483ef76 Compare November 11, 2024 11:28
@quasystaty1 quasystaty1 added this pull request to the merge queue Nov 15, 2024
Merged via the queue into main with commit 01dcf49 Nov 15, 2024
46 checks passed
@quasystaty1 quasystaty1 deleted the quasystaty1/charts/upgrade-celestia-node branch November 15, 2024 09:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants