Files

T

prathamesh 7acabb0743 Add support for generating Helm charts when creating a deployment (#974 )

Part of https://plan.wireit.in/deepstack/browse/VUL-265/

- Added a flag `--helm-chart` to `deploy create` command
- Uses Kompose CLI wrapper to generate a helm chart from compose files in a stack
- To be handled in a follow on PR(s):
  - Templatize generated charts and generate a `values.yml` file with defaults

Reviewed-on: cerc-io/stack-orchestrator#974
Co-authored-by: Prathamesh Musale <prathamesh.musale0@gmail.com>
Co-committed-by: Prathamesh Musale <prathamesh.musale0@gmail.com>

2025-11-27 06:43:07 +00:00

images

stack diagram: fix diagram & compress img

2023-01-20 11:04:24 -05:00

adding-a-new-stack.md

Update links from github.com to git.vdb.to (#732 )

2024-02-06 22:42:44 +00:00

cli.md

rename laconic-sdk to registry-sdk (#897 )

2024-07-31 08:01:02 +00:00

CONTRIBUTING.md

Update links from github.com to git.vdb.to (#732 )

2024-02-06 22:42:44 +00:00

fetching-containers.md

Doc for fetch-containers command

2024-02-27 11:44:28 -07:00

gitea-with-laconicd-fixturenet.md

rename laconic-sdk to registry-sdk (#897 )

2024-07-31 08:01:02 +00:00

helm-chart-generation.md

Add support for generating Helm charts when creating a deployment (#974 )

2025-11-27 06:43:07 +00:00

k8s-deployment-enhancements.md

Add support for k8s pod to node affinity and taint toleration (#917 )

2024-08-15 20:32:58 +00:00

laconicd-with-console.md

Update fixturenet-laconicd stack for renaming changes (#891 )

2024-07-25 08:50:15 +00:00

README.md

Gitea x Laconicd + some doc updates (#549 )

2023-09-27 17:36:12 -04:00

release-process.md

Add release process doc

2023-01-27 21:22:43 -07:00

spec.md

Update links from github.com to git.vdb.to (#732 )

2024-02-06 22:42:44 +00:00

webapp.md

Add doc for deploy-webapp (#672 )

2023-11-29 20:55:14 -07:00

README.md

Stack Orchestrator

Here you will find information about the design of stack orchestrator, contributing to it, and deploying services/applications that combine two or more "stacks".

Most "stacks" contain their own README which has plenty of information on deploying, but stacks can be combined in a variety of ways which are document here, for example: