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

compose: sync kubo with live deployments, bump ceramic to 6.4.0 #496

Merged
merged 3 commits into from
Sep 17, 2024

Conversation

m0ar
Copy link
Contributor

@m0ar m0ar commented Sep 17, 2024

  • Bump the ceramic node to 6.4.0 to get a couple of fixes
    • This is a major because new nodes default to using RECON for tip synchronization, but existing node can continue to use kubo for p2p comms and tip sync.
  • Change the compose cluster versions of kubo to match the ones we are running in the live envs.

Switching around between versions 0.23-0.29 should be fine as they use the same version of the IPFS repo:
https://github.com/ipfs/fs-repo-migrations?tab=readme-ov-file#when-should-i-migrate

@m0ar m0ar added the enhancement New feature or request label Sep 17, 2024
@m0ar m0ar self-assigned this Sep 17, 2024
@m0ar
Copy link
Contributor Author

m0ar commented Sep 17, 2024

Also activated prometheus endpoints for both nodes in preparation for grafana integration, and adds historical sync to the configs. This means (new) nodes will query the p2p network to find streams that happened before it was initialized

@m0ar m0ar merged commit 9850a81 into develop Sep 17, 2024
@m0ar m0ar deleted the m0ar/sync-image-versions branch September 17, 2024 14:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant