Release 0.68.2 by vrutkovs · Pull Request #1918 · VictoriaMetrics/operator

vrutkovs · 2026-03-03T11:05:18Z

No description provided.

cubic-dev-ai

8 issues found across 97 files

Note: This PR contains a large number of files. cubic only reviews up to 75 files per PR, so some files may not have been reviewed.

Prompt for AI agents (unresolved issues)


Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.


<file name="docs/CHANGELOG.md">

<violation number="1" location="docs/CHANGELOG.md:16">
P1: Custom agent: **Changelog Review Agent**

This changelog entry violates the required prefix format: it uses `Dependency` instead of the mandatory `FEATURE`/`BUGFIX`/`SECURITY` prefix (Required structure §1).</violation>

<violation number="2" location="docs/CHANGELOG.md:27">
P1: Custom agent: **Changelog Review Agent**

This modified SECURITY entry is missing the mandatory affected-services section (Required structure §2), so it does not meet changelog format requirements.</violation>

<violation number="3" location="docs/CHANGELOG.md:27">
P3: Fix the trailing punctuation typo: this line has an extra closing parenthesis at the end.</violation>
</file>

<file name="docs/resources/vmagent.md">

<violation number="1" location="docs/resources/vmagent.md:59">
P2: This line references `VMSingle` in VMAgent documentation, which is incorrect and misleading for scrape configuration behavior.</violation>

<violation number="2" location="docs/resources/vmagent.md:73">
P2: The `selectAllByDefault` field is attributed to `VMSingle` instead of `VMAgent`, which misdocuments selector behavior.</violation>

<violation number="3" location="docs/resources/vmagent.md:79">
P2: This selector rule uses `VMSingle` namespaces in VMAgent docs, causing incorrect guidance on namespace scoping.</violation>
</file>

<file name="internal/controller/operator/factory/vmdistributed/vmdistributed_reconcile_test.go">

<violation number="1" location="internal/controller/operator/factory/vmdistributed/vmdistributed_reconcile_test.go:93">
P3: The test case input object is duplicated almost verbatim across scenarios; extract a shared base fixture and override only `VMAuth` per case to reduce maintenance drift.</violation>
</file>

<file name="internal/controller/operator/factory/vmauth/vmauth.go">

<violation number="1" location="internal/controller/operator/factory/vmauth/vmauth.go:661">
P2: Orphan cleanup incorrectly keeps VMServiceScrape when proxy protocol is enabled, leaving stale scrape resources that should be removed.</violation>
</file>

_{Reply with feedback, questions, or to request a fix. Tag @cubic-dev-ai to re-run a review.}

cubic-dev-ai · 2026-03-03T11:23:38Z

docs/CHANGELOG.md

 **Release date:** 23 February 2026

-SECURITY: upgrade Go builder from Go1.25.5 to Go1.25.7. See [the list of issues addressed in Go1.25.7](https://github.com/golang/go/issues?q=milestone%3AGo1.25.7+label%3ACherryPickApproved).)
+* SECURITY: upgrade Go builder from Go1.25.5 to Go1.25.7. See [the list of issues addressed in Go1.25.7](https://github.com/golang/go/issues?q=milestone%3AGo1.25.7+label%3ACherryPickApproved).)


P1: Custom agent: Changelog Review Agent

This modified SECURITY entry is missing the mandatory affected-services section (Required structure §2), so it does not meet changelog format requirements.

Prompt for AI agents

Check if this issue is valid — if so, understand the root cause and fix it. At docs/CHANGELOG.md, line 27: <comment>This modified SECURITY entry is missing the mandatory affected-services section (Required structure §2), so it does not meet changelog format requirements.</comment> <file context> @@ -13,10 +13,18 @@ aliases: **Release date:** 23 February 2026 -SECURITY: upgrade Go builder from Go1.25.5 to Go1.25.7. See [the list of issues addressed in Go1.25.7](https://github.com/golang/go/issues?q=milestone%3AGo1.25.7+label%3ACherryPickApproved).) +* SECURITY: upgrade Go builder from Go1.25.5 to Go1.25.7. See [the list of issues addressed in Go1.25.7](https://github.com/golang/go/issues?q=milestone%3AGo1.25.7+label%3ACherryPickApproved).) * BUGFIX: [vmanomaly](https://docs.victoriametrics.com/operator/resources/vmanomaly/): fix configuration marshalling for [Prophet model](https://docs.victoriametrics.com/anomaly-detection/components/models/#prophet). Previously, using Prophet model would lead to panic during configuration marshalling. </file context>

Suggested change

* SECURITY: upgrade Go builder from Go1.25.5 to Go1.25.7. See [the list of issues addressed in Go1.25.7](https://github.com/golang/go/issues?q=milestone%3AGo1.25.7+label%3ACherryPickApproved).)

* SECURITY: [vmoperator]: upgrade Go builder from Go1.25.5 to Go1.25.7. See [the list of issues addressed in Go1.25.7](https://github.com/golang/go/issues?q=milestone%3AGo1.25.7+label%3ACherryPickApproved).

docs/CHANGELOG.md

docs/resources/vmagent.md

cubic-dev-ai · 2026-03-03T11:23:39Z

docs/resources/vmagent.md


-These objects tell VMAgent from which targets and how to collect metrics and 
-generate part of [VMAgent](https://docs.victoriametrics.com/victoriametrics/vmagent/) scrape configuration.
+These objects specify which targets VMSingle should scrape and how to collect metrics, and generate part of [VMAgent](https://docs.victoriametrics.com/victoriametrics/vmagent/) scrape configuration.


P2: This line references VMSingle in VMAgent documentation, which is incorrect and misleading for scrape configuration behavior.

Prompt for AI agents

Check if this issue is valid — if so, understand the root cause and fix it. At docs/resources/vmagent.md, line 59: <comment>This line references `VMSingle` in VMAgent documentation, which is incorrect and misleading for scrape configuration behavior.</comment> <file context> @@ -56,44 +56,42 @@ Also, you can check out the [examples](https://docs.victoriametrics.com/operator -These objects tell VMAgent from which targets and how to collect metrics and -generate part of [VMAgent](https://docs.victoriametrics.com/victoriametrics/vmagent/) scrape configuration. +These objects specify which targets VMSingle should scrape and how to collect metrics, and generate part of [VMAgent](https://docs.victoriametrics.com/victoriametrics/vmagent/) scrape configuration. -For filtering scrape objects `VMAgent` uses selectors. </file context>

Suggested change

These objects specify which targets VMSingle should scrape and how to collect metrics, and generate part of [VMAgent](https://docs.victoriametrics.com/victoriametrics/vmagent/) scrape configuration.

These objects specify which targets VMAgent should scrape and how to collect metrics, and generate part of [VMAgent](https://docs.victoriametrics.com/victoriametrics/vmagent/) scrape configuration.

internal/controller/operator/factory/vmauth/vmauth.go

docs/CHANGELOG.md

internal/controller/operator/factory/vmdistributed/vmdistributed_reconcile_test.go

vrutkovs · 2026-03-03T11:27:02Z

@AndrewChubatiuk any other fixes we want to add here? PTAL

AndrewChubatiuk · 2026-03-03T11:31:56Z

wanted additionally include #1902

AndrewChubatiuk · 2026-03-03T11:40:45Z

wait, this PR is related to release 0.69

cubic-dev-ai

2 issues found across 5 files (changes from recent commits).

Prompt for AI agents (unresolved issues)


Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.


<file name=".github/workflows/crds.yaml">

<violation number="1" location=".github/workflows/crds.yaml:49">
P0: Dead execution path: The bzip2 command references a non-existent file path. The file was copied as `crd.yaml` in the previous step, not `crd.descriptionless.yaml`. This script will fail when executed because the file doesn't exist at this path.</violation>
</file>

<file name="docs/CHANGELOG.md">

<violation number="1" location="docs/CHANGELOG.md:14">
P1: Custom agent: **Changelog Review Agent**

This change violates the placement clause of the changelog rule: new entries must be kept in the `tip` section, but the `tip` header was replaced with a released-version header.</violation>
</file>

_{Reply with feedback, questions, or to request a fix. Tag @cubic-dev-ai to re-run a review.}

.github/workflows/crds.yaml

docs/CHANGELOG.md

See https://github.com/VictoriaMetrics/VictoriaLogs/releases/tag/v1.46.0

…ruct{} (#1848) util/sets package provides a better interface to handle sets

Ensure that reconciliation doesn't change object resources when no changes to the spec applied

Ensure that controllers correctly stop handling paused objects

Testify asserts produce a significantly better output

…ble set to 100% (#1815) Signed-off-by: Vadim Rutkovsky <vadim@vrutkovs.eu> Co-authored-by: Vadim Rutkovsky <vadim@vrutkovs.eu>

See https://github.com/VictoriaMetrics/VictoriaLogs/releases/tag/v1.47.0

Co-authored-by: cubic-dev-ai[bot] <191113872+cubic-dev-ai[bot]@users.noreply.github.com>

* feat: allow creating vmdistributed without vmauth set Users should be able to provide their own LB instead of VMAuth (taking care of proper switching themselves), so VMAuth should be optional for VMDistributed * updated docs --------- Co-authored-by: Andrii Chubatiuk <andrew.chubatiuk@gmail.com>

* tests: update clientWithActions to record changes for all objects * tests: update tests to use new getTestClient * tests: move ClientWithActions to k8stools * tests: add data update configmap case * test: add daemonset reconcile tests * test: add HPA check case for deployment * test: add tests for HPA actions hpa * test: add tests for httproute reconciliation actions httproute fix httproute * test: add ests for ingress reconciliation action ingress * test: add tests for pdb reconciliation actions pdb * test: add tests for pvc reconciliation acitons * test: add tests for rbac reconciliation * test: add tests for secret reconciliation actions * test: add patch / delete actions * test: add tests for service reconciliation actions service * test: add tests for statefulset reconciliation actions * test: add tests for vmagent reconciliation actions * test: add tests for vmcluster reconciliation actions * test: add tests for vmauth reconciliation vmauth * test: status changes should not cause reconciliation * tests: add vmservicescrape reconcile tests vmservicescrape fix vmservicescrape * comment out tests * test: reduce timeouts and intervals for faster tests * test: add Kind to ClientAction * test: add reconcile tests checking actions and kinds when vmagent is created or updated * fix: sort asserts before creating to make CreateOrUpdate deterministic * test: add reconcile tests for vmalert is created or updated * test: add reconcile tests for vmalertmanager * test: add reconcile tests for vmanomaly * test: add reconcile tests for vmauth * test: add reconcile tests for vmcluster vmcluster * test: vmdistributed reconcile tests * test: vmsingle reconcile tests * test: vtcluster reconcile tests * test: add vtsingle reconcile tests * test: add reconciliation test case for deployment deploy * VMServiceScrape -> VMServiceScrapeForCRD * fix: make updateSTSPVC deterministi * undo vmservicescrape reconcile function renaming --------- Co-authored-by: Andrii Chubatiuk <andrew.chubatiuk@gmail.com>

cubic-dev-ai

2 issues found across 49 files (changes from recent commits).

Prompt for AI agents (unresolved issues)


Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.


<file name="internal/controller/operator/factory/reconcile/reconcile.go">

<violation number="1" location="internal/controller/operator/factory/reconcile/reconcile.go:33">
P3: Update the GoDoc comment to start with `InitDeadlines` so the exported API documentation matches the symbol.

(Based on your team's feedback about documenting exported structs and public methods.) [FEEDBACK_USED]</violation>
</file>

<file name="internal/controller/operator/factory/reconcile/reconcile_test.go">

<violation number="1" location="internal/controller/operator/factory/reconcile/reconcile_test.go:18">
P2: This `init` changes reconcile deadlines for the entire `reconcile` test package and never restores the defaults, which can inadvertently alter the behavior of unrelated tests. Consider scoping the shortened deadlines to `TestWaitForStatus` (with `t.Cleanup` to restore) or using a `TestMain` that resets the globals after running tests.</violation>
</file>

_{Reply with feedback, questions, or to request a fix. Tag @cubic-dev-ai to re-run a review.}

internal/controller/operator/factory/reconcile/reconcile_test.go

internal/controller/operator/factory/reconcile/reconcile.go

…do not have any cleanup tasks (#1902) * reconcile: delete finalizer during reconcile only for resources that do not have any cleanup tasks * reconcile updates - convert NamespacedName to string in logs - update diffDeepDerivative, now slices and maps and considered equal if length of both is 0 (not only of the first maps as it was before), before labels and annotations diff was ignored - do not take PVC metadata diff into account during checking if STS should be recreated since metadata update is covered by a separate function - fixed diffDeep and diffDeepDerivative signature, arguments were swapped before

cubic-dev-ai

1 issue found across 22 files (changes from recent commits).

Prompt for AI agents (unresolved issues)


Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.


<file name="internal/manager/manager.go">

<violation number="1" location="internal/manager/manager.go:235">
P1: The new `reconcile.Init(...)` call wires `statusUpdateTTL` into `statusExpireTTL`, so the configured `controller.statusLastUpdateTimeTTL` no longer updates the actual `LastUpdateTime` TTL logic.</violation>
</file>

_{Reply with feedback, questions, or to request a fix. Tag @cubic-dev-ai to re-run a review.}

internal/manager/manager.go

vrutkovs · 2026-03-04T13:12:38Z

lets bring #1925 in and 🚢 🇮🇹

* do not recreate STS if VCT size was increased decreased and recreate in other cases * do not throw error on STS recreation

cubic-dev-ai

3 issues found across 6 files (changes from recent commits).

Prompt for AI agents (unresolved issues)


Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.


<file name="docs/CHANGELOG.md">

<violation number="1" location="docs/CHANGELOG.md:25">
P1: Custom agent: **Changelog Review Agent**

These new changelog entries violate the changelog rule: they are added in a released section instead of `tip` (Placement rules), and they omit mandatory issue/PR links (Required structure §4 References).</violation>

<violation number="2" location="docs/CHANGELOG.md:25">
P3: Clarify this changelog item to explicitly describe when StatefulSet recreation is skipped vs required, and avoid ambiguous shorthand so users can understand upgrade behavior.

(Based on your team's feedback about clarifying behavior and roles in documentation text.) [FEEDBACK_USED]</violation>
</file>

<file name="internal/controller/operator/factory/reconcile/statefulset_pvc_expand.go">

<violation number="1" location="internal/controller/operator/factory/reconcile/statefulset_pvc_expand.go:134">
P1: Potential nil pointer dereference: `Storage()` returns `*resource.Quantity` which can be nil if storage isn't set. The old code checked `existingSize == nil || newSize == nil`, which was safe. The new code calls `.IsZero()` on potentially nil pointers, which would panic.</violation>
</file>

_{Reply with feedback, questions, or to request a fix. Tag @cubic-dev-ai to re-run a review.}

cubic-dev-ai · 2026-03-04T15:12:55Z

docs/CHANGELOG.md

@@ -11,16 +11,27 @@ aliases:
  - /operator/changelog/index.html


P1: Custom agent: Changelog Review Agent

These new changelog entries violate the changelog rule: they are added in a released section instead of tip (Placement rules), and they omit mandatory issue/PR links (Required structure §4 References).

Prompt for AI agents

Check if this issue is valid — if so, understand the root cause and fix it. At docs/CHANGELOG.md, line 25: <comment>These new changelog entries violate the changelog rule: they are added in a released section instead of `tip` (Placement rules), and they omit mandatory issue/PR links (Required structure §4 References).</comment> <file context> @@ -22,6 +22,8 @@ aliases: * BUGFIX: [vmdistributed](https://docs.victoriametrics.com/operator/resources/vmdistributed/): fix PVC being owned by StatefulSet and top-level object simultaenously. See [#1845](https://github.com/VictoriaMetrics/operator/issues/1845). * BUGFIX: [vmoperator](https://docs.victoriametrics.com/operator/): remove unneeded finalizer from core K8s resources. See [#835](https://github.com/VictoriaMetrics/operator/issues/835). * BUGFIX: [vmdistributed](https://docs.victoriametrics.com/operator/resources/vmdistributed/): remove finalizers from VMServiceScrape and VMPodScrape objects, and keep finalizers on VMAgent, VMCluster, and VMAuth when DeletionTimestamp is not empty. +* BUGFIX: [vmoperator](https://docs.victoriametrics.com/operator/): do not recreate STS if VCT size was increased and recreate in other cases. +* BUGFIX: [vmoperator](https://docs.victoriametrics.com/operator/): wait for STS deletion in case of recreation without throwing an error. </file context>

internal/controller/operator/factory/reconcile/statefulset_pvc_expand.go

cubic-dev-ai · 2026-03-04T15:12:55Z

docs/CHANGELOG.md

+* BUGFIX: [vmdistributed](https://docs.victoriametrics.com/operator/resources/vmdistributed/): fix PVC being owned by StatefulSet and top-level object simultaenously. See [#1845](https://github.com/VictoriaMetrics/operator/issues/1845).
+* BUGFIX: [vmoperator](https://docs.victoriametrics.com/operator/): remove unneeded finalizer from core K8s resources. See [#835](https://github.com/VictoriaMetrics/operator/issues/835).
+* BUGFIX: [vmdistributed](https://docs.victoriametrics.com/operator/resources/vmdistributed/): remove finalizers from VMServiceScrape and VMPodScrape objects, and keep finalizers on VMAgent, VMCluster, and VMAuth when DeletionTimestamp is not empty.
+* BUGFIX: [vmoperator](https://docs.victoriametrics.com/operator/): do not recreate STS if VCT size was increased and recreate in other cases.


P3: Clarify this changelog item to explicitly describe when StatefulSet recreation is skipped vs required, and avoid ambiguous shorthand so users can understand upgrade behavior.

(Based on your team's feedback about clarifying behavior and roles in documentation text.)

View Feedback

Prompt for AI agents

Check if this issue is valid — if so, understand the root cause and fix it. At docs/CHANGELOG.md, line 25: <comment>Clarify this changelog item to explicitly describe when StatefulSet recreation is skipped vs required, and avoid ambiguous shorthand so users can understand upgrade behavior. (Based on your team's feedback about clarifying behavior and roles in documentation text.) </comment> <file context> @@ -22,6 +22,8 @@ aliases: * BUGFIX: [vmdistributed](https://docs.victoriametrics.com/operator/resources/vmdistributed/): fix PVC being owned by StatefulSet and top-level object simultaenously. See [#1845](https://github.com/VictoriaMetrics/operator/issues/1845). * BUGFIX: [vmoperator](https://docs.victoriametrics.com/operator/): remove unneeded finalizer from core K8s resources. See [#835](https://github.com/VictoriaMetrics/operator/issues/835). * BUGFIX: [vmdistributed](https://docs.victoriametrics.com/operator/resources/vmdistributed/): remove finalizers from VMServiceScrape and VMPodScrape objects, and keep finalizers on VMAgent, VMCluster, and VMAuth when DeletionTimestamp is not empty. +* BUGFIX: [vmoperator](https://docs.victoriametrics.com/operator/): do not recreate STS if VCT size was increased and recreate in other cases. +* BUGFIX: [vmoperator](https://docs.victoriametrics.com/operator/): wait for STS deletion in case of recreation without throwing an error. </file context>

Suggested change

* BUGFIX: [vmoperator](https://docs.victoriametrics.com/operator/): do not recreate STS if VCT size was increased and recreate in other cases.

* BUGFIX: [vmoperator](https://docs.victoriametrics.com/operator/): skip StatefulSet recreation when `volumeClaimTemplates` size is increased; recreate StatefulSet for other immutable spec changes.

… or relabelling is set in ingestOnly mode (#1926) Co-authored-by: cubic-dev-ai[bot] <191113872+cubic-dev-ai[bot]@users.noreply.github.com>

vrutkovs marked this pull request as ready for review March 3, 2026 11:07

vrutkovs requested a review from AndrewChubatiuk as a code owner March 3, 2026 11:07

cubic-dev-ai bot reviewed Mar 3, 2026

View reviewed changes

.github/workflows/crds.yaml Outdated Show resolved Hide resolved

docs/CHANGELOG.md Outdated Show resolved Hide resolved

AndrewChubatiuk force-pushed the draft-release-0.68.2 branch from 805e857 to 4224b51 Compare March 3, 2026 16:10

AndrewChubatiuk and others added 14 commits March 3, 2026 21:40

docs: actualize vmdistributed docs (#1844)

a4114bd

Makefile: replace another instance of image with digest

a9ba3dd

Update VictoriaLogs Docker image tag from v1.45.0 to v1.46.0

8eb5355

See https://github.com/VictoriaMetrics/VictoriaLogs/releases/tag/v1.46.0

chore: use k8s.io/apimachinery/pkg/util/sets instead of map[string]st…

e0e4969

…ruct{} (#1848) util/sets package provides a better interface to handle sets

tests: create idempotency tests (#1880)

4140445

Ensure that reconciliation doesn't change object resources when no changes to the spec applied

tests: add tests checking paused status (#1879)

dab66a7

Ensure that controllers correctly stop handling paused objects

tests: replace most t.Fatalf calls (#1883)

0b2cb39

Testify asserts produce a significantly better output

reconcile: perform pods deletion instead of eviction with maxUnavaila…

0cf0ac2

…ble set to 100% (#1815) Signed-off-by: Vadim Rutkovsky <vadim@vrutkovs.eu> Co-authored-by: Vadim Rutkovsky <vadim@vrutkovs.eu>

Update VictoriaLogs Docker image tag from v1.46.0 to v1.47.0

5e17cd2

See https://github.com/VictoriaMetrics/VictoriaLogs/releases/tag/v1.47.0

vmpodscrape: fixed vmpodscrape port for vlagent and vmagent (#1888)

9ad08c7

Co-authored-by: cubic-dev-ai[bot] <191113872+cubic-dev-ai[bot]@users.noreply.github.com>

docs: added paragraph about vmsingle scraping (#1895)

1485ec1

docs: update CHANGELOG

6f24dae

restore descriptions in crd.yaml that is published to releases

0c393c3

AndrewChubatiuk force-pushed the draft-release-0.68.2 branch from 4224b51 to 0c393c3 Compare March 3, 2026 19:41

AndrewChubatiuk and others added 2 commits March 3, 2026 22:08

vmagent: removed rbac migration function (#1886)

9c9d295

cubic-dev-ai bot reviewed Mar 3, 2026

View reviewed changes

internal/controller/operator/factory/reconcile/reconcile_test.go Outdated Show resolved Hide resolved

internal/controller/operator/factory/reconcile/reconcile.go Outdated Show resolved Hide resolved

AndrewChubatiuk added 3 commits March 3, 2026 22:36

vlogs: removed unused code (#1896)

9ed2359

removed finalizer from core k8s resources (#1839)

55fe068

AndrewChubatiuk force-pushed the draft-release-0.68.2 branch from 8938d70 to 401b5fe Compare March 3, 2026 21:00

CHANGELOG: move finalizer package entry to the tip

21930f9

cubic-dev-ai bot reviewed Mar 4, 2026

View reviewed changes

internal/manager/manager.go Show resolved Hide resolved

address cubic comments

935cbd1

AndrewChubatiuk force-pushed the draft-release-0.68.2 branch from 0fe5bf9 to 935cbd1 Compare March 4, 2026 07:31

reconcile: updated conditions for STS recreate (#1925)

b0b78e2

* do not recreate STS if VCT size was increased decreased and recreate in other cases * do not throw error on STS recreation

cubic-dev-ai bot reviewed Mar 4, 2026

View reviewed changes

AndrewChubatiuk and others added 3 commits March 4, 2026 17:52

undo IsZero check for PVC storage size (#1928)

0deda0a

vm{agent,single}: do not mount scrape secret, when stream aggregation…

1508bf8

… or relabelling is set in ingestOnly mode (#1926) Co-authored-by: cubic-dev-ai[bot] <191113872+cubic-dev-ai[bot]@users.noreply.github.com>

docs: update release date in CHANGELOG

7cd1303

AndrewChubatiuk approved these changes Mar 4, 2026

View reviewed changes

vrutkovs merged commit 44e7578 into release-0.68 Mar 4, 2026
4 checks passed

vrutkovs deleted the draft-release-0.68.2 branch March 4, 2026 17:51

	* SECURITY: upgrade Go builder from Go1.25.5 to Go1.25.7. See [the list of issues addressed in Go1.25.7](https://github.com/golang/go/issues?q=milestone%3AGo1.25.7+label%3ACherryPickApproved).)
	* SECURITY: [vmoperator]: upgrade Go builder from Go1.25.5 to Go1.25.7. See [the list of issues addressed in Go1.25.7](https://github.com/golang/go/issues?q=milestone%3AGo1.25.7+label%3ACherryPickApproved).

	These objects specify which targets VMSingle should scrape and how to collect metrics, and generate part of [VMAgent](https://docs.victoriametrics.com/victoriametrics/vmagent/) scrape configuration.
	These objects specify which targets VMAgent should scrape and how to collect metrics, and generate part of [VMAgent](https://docs.victoriametrics.com/victoriametrics/vmagent/) scrape configuration.

		@@ -11,16 +11,27 @@ aliases:
		- /operator/changelog/index.html

	* BUGFIX: [vmoperator](https://docs.victoriametrics.com/operator/): do not recreate STS if VCT size was increased and recreate in other cases.
	* BUGFIX: [vmoperator](https://docs.victoriametrics.com/operator/): skip StatefulSet recreation when `volumeClaimTemplates` size is increased; recreate StatefulSet for other immutable spec changes.

Conversation

vrutkovs commented Mar 3, 2026

Uh oh!

cubic-dev-ai bot left a comment

Choose a reason for hiding this comment

Uh oh!

cubic-dev-ai bot Mar 3, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Uh oh!

cubic-dev-ai bot Mar 3, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Uh oh!

vrutkovs commented Mar 3, 2026

Uh oh!

AndrewChubatiuk commented Mar 3, 2026

Uh oh!

AndrewChubatiuk commented Mar 3, 2026

Uh oh!

cubic-dev-ai bot left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

cubic-dev-ai bot left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

cubic-dev-ai bot left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

vrutkovs commented Mar 4, 2026

Uh oh!

cubic-dev-ai bot left a comment

Choose a reason for hiding this comment

Uh oh!

cubic-dev-ai bot Mar 4, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

cubic-dev-ai bot Mar 4, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

cubic-dev-ai bot Mar 3, 2026 •

edited

Loading

cubic-dev-ai bot Mar 3, 2026 •

edited

Loading

cubic-dev-ai bot Mar 4, 2026 •

edited

Loading

cubic-dev-ai bot Mar 4, 2026 •

edited

Loading