jakman85andClaude Opus 4.8
22db5fdb63
- HR chart 3.3.x -> 3.9.x (Kyverno v1.13.6 -> v1.19.0). - crds.install:false + CRDs pre-applied server-side (5.7 MB bundle exceeds kubectl's 256 KB annotation limit; Helm client-side apply would stall the platform Kustomization, kps-style). - CLI lockstep (ci/conformance/devcontainer versions.env + run-l0.sh default) -> 1.19.0. Pre-verified: v1.19.0 kyverno CLI passes the L0 suite 17/17 with the existing test format. - Policies are kyverno.io/v1 ClusterPolicy (stable API, unchanged in v1.19). Co-Authored-By: Claude Opus 4.8 <[email protected]>
27 lines
1.1 KiB
Bash
27 lines
1.1 KiB
Bash
# ci/versions.env — pinned tool versions (R-TEST-02: reproducible, version-pinned)
|
|
#
|
|
# Single source of truth for every tool the gate invokes. The Gitea Actions
|
|
# workflow and the local scripts both source this file so CI and a laptop run
|
|
# the exact same versions. Bump deliberately; a version change is a code change
|
|
# that must go through the normal feature-branch -> main gate.
|
|
#
|
|
# Owner: WS-GITOSS (CI). The Kyverno/Chainsaw versions MUST stay in lockstep with
|
|
# whatever platform/kyverno and conformance/ pin — see integration notes in README.
|
|
|
|
# L0 policy gate (Kyverno CLI) + ServiceDefinition validation (kyverno-json)
|
|
KYVERNO_VERSION="1.19.0"
|
|
KYVERNO_JSON_VERSION="0.0.3"
|
|
|
|
# L1/L2/L3 declarative runner (Chainsaw) — invoked via conformance/ entrypoint,
|
|
# pinned here so a local run matches CI even before the in-cluster Job exists.
|
|
CHAINSAW_VERSION="0.2.12"
|
|
|
|
# Lint / manifest tooling
|
|
YAMLLINT_VERSION="1.35.1"
|
|
KUBECTL_VERSION="1.36.4"
|
|
YQ_VERSION="4.44.6"
|
|
|
|
# ServiceDefinition JSON-Schema validation (schemas/validate.sh). Pip-installed;
|
|
# pinned here so CI and a laptop validate against the exact same validator.
|
|
CHECK_JSONSCHEMA_VERSION="0.29.4"
|