Our current 8Knot deployment on Openshift requires manual intervention to rebuild and reconfigure microservices.
The optimization for this is to configure a Helm chart for 8Knot so that the architecture can be audited (open deployment) and is editable as code (rather than via oc, kubectl, or Openshift UI).
Because docker-compose and Helm charts are similar, there are also tools that can help translate docker-compose to Helm. Kompose is one of those tools- it doesn't guarantee that the resulting Helm chart will be perfect, but it should be very nearly correct.
This will be nice to have, because we can write one artifact (the compose yaml file) and automatically generate the Helm chart, reducing the complexity of our deployments. This has the added benefit of allowing users to deploy 8Knot instances on a single box (via docker-compose) or via helm on an orchestration platform without custom manual deployment documentation.
JamesKunstle
commented
1 year ago
Our current 8Knot deployment on Openshift requires manual intervention to rebuild and reconfigure microservices.
The optimization for this is to configure a Helm chart for 8Knot so that the architecture can be audited (open deployment) and is editable as code (rather than via oc, kubectl, or Openshift UI).
Because docker-compose and Helm charts are similar, there are also tools that can help translate docker-compose to Helm. Kompose is one of those tools- it doesn't guarantee that the resulting Helm chart will be perfect, but it should be very nearly correct.
This will be nice to have, because we can write one artifact (the compose yaml file) and automatically generate the Helm chart, reducing the complexity of our deployments. This has the added benefit of allowing users to deploy 8Knot instances on a single box (via docker-compose) or via helm on an orchestration platform without custom manual deployment documentation.