cerc-io
/
stack-orchestrator
mirror of https://github.com/cerc-io/stack-orchestrator
1
0
Fork 0
Code Issues Actions Packages Projects Releases Wiki Activity
stack-orchestrator/docs
History
prathamesh0 4977e3ff43
Publish / Gate: k8s deploy e2e (push) Failing after 3s Details
Deploy Test / Run deploy test suite (push) Failing after 0s Details
Publish / Build and publish (push) Has been skipped Details
K8s Deployment Control Test / Run deployment control suite on kind/k8s (push) Failing after 0s Details
Webapp Test / Run webapp test suite (push) Failing after 0s Details
Smoke Test / Run basic test suite (push) Failing after 0s Details
Lint Checks / Run linter (push) Failing after 0s Details
K8s Deploy Test / Run deploy test suite on kind/k8s (push) Failing after 0s Details
k8s: manage Caddy ingress image via spec (so-p3p) (#749) 
Closes so-p3p:
- New spec key `caddy-ingress-image`: on fresh install, deploys Caddy with this image; on subsequent `deployment start`, patches the running Caddy Deployment if the image differs. Defaults to the manifest's hardcoded image when absent
- When the spec key is absent, SO does **not** touch a running Caddy — avoids silently reverting an image set out-of-band (ansible playbook, another deployment's spec)
- `strategy: Recreate` on the Caddy Deployment manifest (required — hostPort 80/443 deadlocks rolling updates)
- Reconcile runs under both `--perform-cluster-management` and the default `--skip-cluster-management` (it's a k8s-API patch, not a cluster-lifecycle op)
- Image template by container name rather than string match, so the spec override wins regardless of what the shipped manifest hardcodes
- Cluster-scoped caveat documented: `caddy-system` is shared across deployments, so the last `deployment start` that sets the key wins for everyone
 		2026-04-21 14:40:39 +05:30
..
images stack diagram: fix diagram & compress img 2023-01-20 11:04:24 -05:00
CONTRIBUTING.md Migrate canonical source from Gitea to GitHub (#738) 2026-04-02 10:58:14 +05:30
README.md Gitea x Laconicd + some doc updates (#549) 2023-09-27 17:36:12 -04: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 Add Job and secrets support for k8s-kind deployments (#995) 2026-03-11 03:56:21 +00:00
deployment_patterns.md k8s: manage Caddy ingress image via spec (so-p3p) (#749) 2026-04-21 14:40:39 +05:30
docker-compose-deployment.md Add Docker Compose deployment guide 2026-01-17 18:17:01 -05:00
fetching-containers.md Apply pre-commit linting fixes 2026-01-20 23:16:44 -05:00
gitea-with-laconicd-fixturenet.md Apply pre-commit linting fixes 2026-01-20 23:16:44 -05: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 Apply pre-commit linting fixes 2026-01-20 23:16:44 -05:00
laconicd-with-console.md Update fixturenet-laconicd stack for renaming changes (#891) 2024-07-25 08:50:15 +00:00
release-process.md Apply pre-commit linting fixes 2026-01-20 23:16:44 -05:00
spec.md Apply pre-commit linting fixes 2026-01-20 23:16:44 -05:00
webapp.md Apply pre-commit linting fixes 2026-01-20 23:16:44 -05: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: