jakman85andClaude Opus 4.8
cbc2301b30
Text-only cleanup after the upgrade campaign. Updates stale version strings, prose, and comments to the verified current facts; no Kubernetes behavior or version pins changed except the kubectl toolchain bump (below). Verified facts applied: k3s v1.36.4+k3s1, Debian 13 trixie, Cilium 1.20.1 / Gateway API v1.6.1, Longhorn 1.12.1, node RAM 24 GiB, dedicated virtio2 SSD etcd disk per node, Velero chart 12.x / v1.18, Grafana 13.2.0. - Version strings across infra/ and platform/ READMEs + comments - kubectl toolchain 1.31.4 -> 1.36.4 (devcontainer/ci/conformance versions.env; 1.31 vs a 1.36 cluster exceeded the +-1 skew) - Retired-single-apps-Kustomization refs -> apps-wave-0/1/2 + apps-vms with per-wave SOPS decryption (flux/clusters docs + bootstrap.sh) - COMPLETED/historical banners on the three executed plan docs - Resolved TODO(WS-SEC) markers -> Renovate-maintained ranges - Appended dated DECISIONS-LOG entry (2026-08-30) superseding the 2026-08-26 LIVE STATE line Left as revalidation items (not blind-edited): external-snapshotter v8.2.0 vs 1.36, Cilium ext_authz/forward-auth relevance under 1.20.1, conformance ImageVolume feature-gate assertions under 1.36. Co-Authored-By: Claude Opus 4.8 <[email protected]>
32 lines
1.6 KiB
Bash
32 lines
1.6 KiB
Bash
# Pinned toolchain for the home-network-k3s dev container (the reproducible baseline).
|
|
# The non-Python prereqs (OpenTofu, age, sops, flux) are Go binaries, so — per the
|
|
# operator's rule — they are baked into a container image instead of a venv. The
|
|
# conformance test toolchain (kyverno CLI, kyverno-json, chainsaw, yamllint,
|
|
# check-jsonschema, yq) is likewise baked in so `make -C ci gate` runs here == in CI.
|
|
#
|
|
# NOTE: these are best-effort pins; bump to current stable if a download 404s at build.
|
|
# The conformance-tool versions below MUST stay in lockstep with ci/versions.env.
|
|
FEDORA_VERSION=44
|
|
OPENTOFU_VERSION=1.9.0
|
|
AGE_VERSION=1.2.1
|
|
SOPS_VERSION=3.9.4
|
|
FLUX_VERSION=2.4.0
|
|
# Aligned with ci/versions.env (KUBECTL=1.36.4) and the k3s 1.36.4 cluster.
|
|
KUBECTL_VERSION=1.36.4
|
|
HELM_VERSION=3.16.0
|
|
|
|
# --- Conformance test toolchain (match ci/versions.env) ----------------------
|
|
KYVERNO_VERSION=1.13.4
|
|
# ci/versions.env pins KYVERNO_JSON_VERSION=0.0.5, but NO such release exists:
|
|
# kyverno/kyverno-json's highest tag is v0.0.3 (git ls-remote --tags), and the
|
|
# platform's own platform/kyverno/scripts/run-l0.sh already defaults to v0.0.3.
|
|
# 0.0.5 is an erroneous pin in ci/versions.env — flagged to PM to correct there.
|
|
# We bake the real, platform-aligned v0.0.3 so the image builds. kyverno-json is
|
|
# NOT invoked by any static gate stage (ci/l0.sh uses `kyverno test` + check-jsonschema).
|
|
KYVERNO_JSON_VERSION=0.0.3
|
|
CHAINSAW_VERSION=0.2.12
|
|
YAMLLINT_VERSION=1.35.1
|
|
YQ_VERSION=4.44.6
|
|
CHECK_JSONSCHEMA_VERSION=0.29.4
|
|
# Proxmox provider (bpg/proxmox) is pinned in the tofu module (infra/tofu/versions.tf), not here.
|