Delivery manifests, policies and runbooks for every Telekabin service.
- JavaScript 80.2%
- Open Policy Agent 19.8%
|
All checks were successful
Engineering delivery / Validate and deliver manifests (push) Successful in 1m6s
|
||
|---|---|---|
| .forgejo | ||
| deploy | ||
| ops | ||
| .gitleaks.toml | ||
| catalog-info.yaml | ||
| CODEOWNERS | ||
| CONTRIBUTING.md | ||
| mkdocs.yml | ||
| README.md | ||
| SECURITY.md | ||
telekabin-deploy
Delivery manifests for every Telekabin service.
| Path | Purpose |
|---|---|
deploy/base/ |
One directory per service: workload, Service and disruption budget |
deploy/overlays/dev |
Deployed from branch dev |
deploy/overlays/test |
Deployed from branch test |
deploy/overlays/production |
Deployed from branch main |
ops/ |
Policies, alert rules and runbooks |
Images are built once; the tag of each service lives in its base kustomization.yaml, so it moves between environments by merging dev into test and test into main. Runtime values live in overlays/<env>/runtime/*.env.
Routes
deploy/overlays/<env>/routes.yaml attaches HTTPRoutes to the shared edge gateway. Hostnames are <name>.<env>.telekabin.localhost; production drops the environment label.
Promotion
- Work lands on
devand deploys to the dev environment. - A pull request from
devtotestpromotes it after a soak. - A pull request from
testtomainpromotes it to production. - Rollback is a revert on the branch of the affected environment.