Skip to content

chore(deploy): move onto schema 0.22.0 and the republished context - #33

Merged
ExtraToast merged 1 commit into
mainfrom
chore/schema-0.22.0
Aug 26, 2026
Merged

chore(deploy): move onto schema 0.22.0 and the republished context#33
ExtraToast merged 1 commit into
mainfrom
chore/schema-0.22.0

Conversation

@ExtraToast

Copy link
Copy Markdown
Contributor

Moves this repository onto schema 0.22.0 and the cluster context republished at that version, cluster-deploy-context-public@sha256:e839b908…. The context was published from homelab-inventory#16 first, because the toolkit asserts the context declares exactly the installed version.

Behaviour changes checked before bumping

0.21/0.22 change two things that affect rendered output. Both were checked against the live cluster.

Workloads now render container probes from the health block they already declare. This is the 0.21.0 feature; nothing new is required in the manifest.

stateful: true no longer selects a StatefulSet — the controller kind must be declared explicitly. Only knowledge-ingest-worker declares stateful anywhere in the estate, and it runs as a Deployment in-cluster today, so 0.22.0's render is a correction rather than a regression.

Verification

The deploy-artifact path was replayed locally against the new context: toolkit 0.22.0 installed from GitHub Packages, the context pulled by digest with oras, and deploy-check at v0.16.1. exit=0, no failing gates, apply bundle emitted for production.

The toolkit asserts the cluster context declares exactly the installed version,
so the context was republished at 0.22.0 first (homelab-inventory#16) and this
repository now pins that digest.

0.21/0.22 render container probes from the health block a workload already
declares, and stop selecting a StatefulSet from stateful: true. Neither needs a
change here: no workload in this repository declares stateful, and the probe
paths were checked against the live cluster.

Verified by replaying the deploy-artifact path locally against the new context
with toolkit 0.22.0 and deploy-check v0.16.1: exit 0, no failing gates, apply
bundle emitted.
@ExtraToast ExtraToast added the type: chore Maintenance work without intended behavior change. label Aug 26, 2026
@ExtraToast ExtraToast self-assigned this Aug 26, 2026
@github-actions

Copy link
Copy Markdown

Deploy Preview — auth-ui

Environments: production
Context ref: ghcr.io/jorisjonkers-dev/cluster-deploy-context-public@sha256:e839b90839a5f33f1038d305531d9bb2cd85a3a627a436c395c4116533321cc9
Workloads: 1 | Routes: 1 | Gatus endpoints: 1

Image refs

  • auth-ui: ghcr.io/jorisjonkers-dev/auth-ui@sha256:0000000000000000000000000000000000000000000000000000000000000000

SC-11 Readiness Scorecard

Check Status Detail
schema_pinned pass
context_pinned pass
no_latest_images pass
health_declared pass
route_owner_authmode_declared pass
rollback_retention_acknowledged pass
no_raw_secrets pass
stateful_policy_declared not_applicable deployment declares no stateful workloads
raw_manifests_guarded not_applicable no workload enables rawManifests
npm_signatures_verified not_applicable provenance is only evaluated when publishing an artifact

pass = ready · fail = blocks deployment · not_applicable = check does not apply

➖ 3 check(s) not applicable: stateful_policy_declared, raw_manifests_guarded, npm_signatures_verified


Updated by deploy-check on push to this PR.

@ExtraToast
ExtraToast merged commit bb00533 into main Aug 26, 2026
9 checks passed
@ExtraToast
ExtraToast deleted the chore/schema-0.22.0 branch August 26, 2026 12:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

type: chore Maintenance work without intended behavior change.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant