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

Provide CorDapps to containers deployment options #2

Open
henrikr3 opened this issue Feb 3, 2020 · 0 comments
Open

Provide CorDapps to containers deployment options #2

henrikr3 opened this issue Feb 3, 2020 · 0 comments
Labels
enhancement New feature or request

Comments

@henrikr3
Copy link
Contributor

henrikr3 commented Feb 3, 2020

Currently CorDapps are copied to the Corda Node container once it is running to the persistent storage assigned to that pod. The CorDapps should ideally be segregated.

a) Init containers
We could deploy the CorDapps to the Corda Node pod by use of init containers to install the CorDapps before the pod starts up:
https://kubernetes.io/docs/concepts/workloads/pods/init-containers/
This would essentially work as such:

  • Corda Node is deployed to Kubernetes cluster
  • Corda Node init container is automatically launched
  • Corda Node init container starts up and downloads CorDapps assigned to be loaded to the Corda Node from a dedicated distribution site on for example Azure Storage or Amazon S3.
  • Once init container has completed successfully (verifiably installed the CorDapps), the Corda Node will start up with the CorDapps already available

b) Other options could be considered as well:

A few options could be defined in Helm charts as options that the user can select from for deploying CorDapps.

@henrikr3 henrikr3 added the enhancement New feature or request label Feb 3, 2020
henrikr3 pushed a commit that referenced this issue Apr 7, 2020
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

No branches or pull requests

1 participant