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

[IMPLEMENTATION]-[TESTNET] Writing K8s Deployments and Services #89

Open
3 tasks
SundarGowtham opened this issue Apr 30, 2024 · 0 comments
Open
3 tasks
Assignees

Comments

@SundarGowtham
Copy link
Collaborator

Scoping the exact requirements and details for Kubernetes Deployments and the Kuberentes Services

[Implementation] - Writing Kubernetes Yaml files for Kubernetes Deployments and the Kuberentes Services

This ticket holds the implementation details required for building the Kubernetes Deployments and the Kuberentes Services for the following components

1. Summary

As shown in the LLD for the Segregated Testnet, we will be writing the Deployments and Services using the template provided there.

These the components will be written in yaml:

  • Bitcoin regtest node
  • Stacks node (as a miner)
  • N amount of instances of the Nakamoto signer
  • Stacks block explorer
  • Stacks API
  • Mempool.space Frontend
  • Mempool.space Backend
  • Electrum Server

sBTC Components (Cannot be written in yaml yet)

  • M instances of the signer binary (sBTC component)
  • sBTC Bridge Frontend (sBTC component)
  • sBTC Bridge Backend (sBTC component)
  • M instances of BlockList API (sBTC component)
  • Transaction Sponsorship API (sBTC component)

The sBTC components is still undetermined since we have not built those components yet but when it is done, then this ticket can be considered completed.

2 External Resources

Closing Checklist

  • The takeaway from this issue is clearly documented in the description of this ticket.
  • Everyone necessary has reviewed the resolution and agrees with the takeaways.
  • This ticket has or links all the information necessary to familiarize a contributor with the topic and how it was resolved.
@SundarGowtham SundarGowtham self-assigned this Apr 30, 2024
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

1 participant