Current gap:
Release data is split across Helm Charts, Image Tags, Changelogs, and Test runs. A version tag does not show which exact package is passed together.
Change:
Build the candidate chart packages, test those exact files, and publish the same files with one generated JSON record.
- Record the Operator chart, CRD chart, Operator image, and config-reloader image digests.
- Record the Kubernetes version and the Operator and chart versions used before the upgrade.
Example:
chart 0.67.2 with default values, CRD chart 0.14.0, rendered-manifest digest X, Operator and config-reloader v0.74.1, Kubernetes version Y, upgrade source Z, result PASS.
PASS means that the full-package test - described in #2493 - passed for this exact package and upgrade source.
Done when:
Every release changelog links to one record created by the successful package test.
Product result:
A customer can answer: "Was this exact package tested, and where is the result?"
Current gap:
Release data is split across Helm Charts, Image Tags, Changelogs, and Test runs. A version tag does not show which exact package is passed together.
Change:
Build the candidate chart packages, test those exact files, and publish the same files with one generated JSON record.
Example:
chart
0.67.2with default values, CRD chart0.14.0, rendered-manifest digest X, Operator and config-reloaderv0.74.1, Kubernetes version Y, upgrade source Z, result PASS.Done when:
Every release changelog links to one record created by the successful package test.
Product result:
A customer can answer: "Was this exact package tested, and where is the result?"