Skip to content
imlostincode
ENNL
Deployment kit

astro-k8s-deployment-kit

Shared deploy setup for Astro sites. Fix it once, and every site picks it up on its next update.

v1.2.2

  • A published release, or a change to the README, docs/, examples/ or imlostincode.json on main, asks imlostincode.com to rebuild, so the docs there stay current. No changes to the kit itself.
Docs for this version →

v1.2.1

Docs for this version →

v1.2.0

Docs for this version →

v1.1.0

Fixes found onboarding the template's first consumer. Additive — no interface changes, so ?ref= and uses: …@ bumps are drop-in from v1.0.0.

Per-arch build tags no longer shadow the release tag

The matrix pushed <version>-amd64 / <version>-arm64 and joined them into <version>. All three sort identically under a Flux ImagePolicy anchored on the version prefix, so ImageUpdateAutomation could pick a per-arch tag — a single-arch image that will not run on the other architecture's nodes. Observed in practice, self-correcting only by luck of ordering.

Scaffolding tags are now buildstage-<arch>-<version>. Version last means an anchored filter cannot match them; Go RE2 has no lookahead, so excluding the suffix in-pattern was not possible.

Upgrading: nothing to change if your filterTags pattern is anchored with ^. Old <version>-<arch> tags from previous releases stay in the registry and are harmless — delete them if you want the package tidy.

Cache export failure no longer fails the build

cache-to: type=registry writes into the project's own GHCR package. A failed cache export failed the whole run even after the image pushed successfully — which is what a first-ever deploy does, since there is no package yet. ignore-error=true on all three workflows.

Documentation

  • The four tags a release publishes and which one is deployable.
  • The GHCR package permission model: an unlinked package is hidden from the repository's Packages tab, so it looks absent, and granting packages: write does not help because the token is not what is being refused.
  • general-secrets does not create ghcr-login-secret in every app namespace — it is a hand-maintained per-cluster list, and a missing entry fails as an anonymous pull with 401.
Docs for this version →

v1.0.0

Docs for this version →