You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently we can easily spin up our container with docker-compose. This is very fine for small environments or single hosts. If you want to run it in Container Orchestrator like Kubernetes we need to adopt their Deployment Mechanisms.
The first answer would be to create RAW Kubernetes Manifests and handle this for our container. That would work but in future it's hard to add their templating.
Since we shipping our Indy Node as Container we should also ship the Manifests as a full package for options. Luckily there is a Standard for this use case and it's https://helm.sh/.
Description of Done
Implement a small PoC of 4 Nods like in docker-compose and test if they can connect to each other like in our docker-compose
Implement a small smoke test for Helm Deployment
The text was updated successfully, but these errors were encountered:
Description
Currently we can easily spin up our container with docker-compose. This is very fine for small environments or single hosts. If you want to run it in Container Orchestrator like Kubernetes we need to adopt their Deployment Mechanisms.
The first answer would be to create
RAW
Kubernetes Manifests and handle this for our container. That would work but in future it's hard to add their templating.Since we shipping our Indy Node as Container we should also ship the Manifests as a full package for options. Luckily there is a Standard for this use case and it's https://helm.sh/.
Description of Done
The text was updated successfully, but these errors were encountered: