VictoriaMetrics / VictoriaMetrics/operator

Tested Release Record

Open
#2,492 2 comments 0 reactions 1 assignee View on GitHub

@AquaOctet is already working on this.

Since Aug 21, 2026.

Dominant language
Go
Stars
589
Forks
229
Avg merge
1d 9h
Merged PRs (30d)
77

Description

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?"

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.