Files
OKF_CV_Website/architecture/delivery.md
T
Noel SabiaandClaude Opus 5.5 64fef83314 docs(okf): move bundle to repo root and retire brief
The brief is fully captured in the bundle; it stays in git history.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-11 14:22:03 +02:00

38 lines
1.5 KiB
Markdown

---
type: Pipeline
title: Delivery
description: Gitea Actions on the home server scan, build, push to the Gitea registry, deploy with kubectl, and version with release-please.
tags: [architecture, ci, gitea, release-please]
status: stable
generated: { by: claude-code/claude-opus-5-5, at: 2026-10-11T12:15:30Z }
---
# Pipeline
```
push to main ─► Gitea Actions (runner on the home server)
├─ go test ./...
├─ snyk test
├─ build images: gateway (with Nuxt), chapter
├─ push to the Gitea container registry
└─ kubectl apply -k deploy/
─► release-please (Gitea variant) opens a release PR; merging it tags the version
```
# Details
- **Commits:** Conventional Commits. `feat:` bumps minor, `fix:` bumps patch,
`docs:` and `chore:` do not release.
- **Image tags:** the git SHA, so every deploy is traceable.
- **Registry pull:** k3s needs an `imagePullSecret` for the Gitea registry,
or `/etc/rancher/k3s/registries.yaml` if the registry is plain HTTP.
- **Runner permissions:** a kubeconfig for a ServiceAccount that can only
manage resources in `cv`.
- **Jobs are immutable:** changing a completed chapter's Job spec needs a
delete before apply. Rare, since finished chapters do not change.
- **Snyk:** needs a `SNYK_TOKEN` secret in Gitea.
# Later
- k6 as a release gate needs a staging target. See [open questions](/decisions/open-questions.md).