Delivery manifests, policies and runbooks for every Telekabin service.
  • JavaScript 80.2%
  • Open Policy Agent 19.8%
Find a file
Arman Rad 5b9a5d2a90
All checks were successful
Engineering delivery / Validate and deliver manifests (push) Successful in 1m6s
Merge pull request 'Release to production: service catalog and documentation' (#274) from test into main
2026-10-26 23:26:35 +00:00
.forgejo chore(deps): update conftest to v0.71.1 2026-10-13 15:57:53 +03:30
deploy perf(app-functions): raise memory limit to 1Gi 2026-10-25 12:04:00 +03:30
ops docs(portal): register entities and publish docs to the engineering portal 2026-10-26 23:23:34 +00:00
.gitleaks.toml ci: scan for secrets with gitleaks 2025-12-07 14:58:56 +03:30
catalog-info.yaml docs(portal): register entities and publish docs to the engineering portal 2026-10-26 23:23:34 +00:00
CODEOWNERS chore: add CODEOWNERS 2025-06-22 10:17:11 +03:30
CONTRIBUTING.md docs: describe how to contribute 2025-04-28 15:23:05 +03:30
mkdocs.yml docs(portal): register entities and publish docs to the engineering portal 2026-10-26 23:23:34 +00:00
README.md feat(routes): expose every environment through the shared gateway 2026-06-26 15:55:21 +03:30
SECURITY.md docs: add security policy 2025-11-19 15:20:15 +03:30

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

  1. Work lands on dev and deploys to the dev environment.
  2. A pull request from dev to test promotes it after a soak.
  3. A pull request from test to main promotes it to production.
  4. Rollback is a revert on the branch of the affected environment.