TazLab K8s Image Automation
Flux automates image updates for critical workloads. This ensures the cluster follows the CI pipeline without manual intervention.
Active Image Policies
| App | Namespace | Repository | Policy Rule |
|---|---|---|---|
| hugo-blog | hugo-blog | tazzo/tazlab-blog (Docker Hub) | blog-<N>-... (Numerical Asc) |
| hugo-wiki | hugo-wiki | tazzo/tazlab-wiki (Docker Hub) | wiki-<N>-... (Numerical Asc) |
| mnemosyne | tazlab-db | tazzo/mnemosyne-mcp (Docker Hub) | mcp-<N>-... (Numerical Asc) |
| teaching | teaching | tazzo/tazlab-teaching (Docker Hub) | teaching-<N>-... (Numerical Asc) |
| ambrogio-site | ambrogio-site | tazzo/tazlab-ambrogio-site (Docker Hub) | ambrogio-site-<N>-... (Numerical Asc) |
| halloween | halloween | tazzo/tazlab-halloween (Docker Hub) | halloween-<N>-... (Numerical Asc) |
| homepage | flux-system | ghcr.io/gethomepage/homepage | semver >=2.1.2 (already bumped to v2.2.0 live) |
Automation Artifacts
- Definitions:
infrastructure/automation/<app>/automation.yaml. - Commits: Flux bot commits directly to
master. - Markers: Look for
# {"$imagepolicy": "flux-system:<app>"}in Deployment manifests.
Model variance: the three original pipelines use Docker Hub with numerical run-number tags; the homepage pipeline (added 2026-08, commit 00a2b99) uses GHCR with semantic versioning. Both are supported by Flux ImagePolicy. See Homepage Dashboard for the outage that motivated the homepage pipeline.
See Also
- DAG: Flux DAG
- Detail: Image Automation Detail — exact pipeline specs
- Hub: TazLab K8s Hub