introduce VMAnomalyConfig by AndrewChubatiuk · Pull Request #1472 · VictoriaMetrics/operator

AndrewChubatiuk · 2025-07-17T08:33:50Z

starting 1.25.0 anomaly supports hot-reload, and this PR introduces VMAnomalyConfig CR, that allows to add extra models, schedulers and queries for VMAnomaly dynamic configuration

f41gh7

It's required to add documentation in first place. Is it possible that model could interfere on each other? Is it required to config VMAnomaly itself somehow? What is a relations between VMAnomaly and VMAnomalyModel?

Currently it's not possible to use this new API.

Also, I suggest to add -configCheckInterval to the vmanomaly in the same way as other components have it. It solves configuration reload without need of external config reloaders.

AndrewChubatiuk · 2025-07-18T11:59:37Z

removed config reloader since python watchdog, which implements hot reload listens to fs events

AndrewChubatiuk · 2025-07-29T13:20:12Z

added scheduler CR, added docs

Copilot

Pull request overview

Copilot reviewed 36 out of 36 changed files in this pull request and generated no new comments.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

cubic-dev-ai

8 issues found across 31 files

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/vmanomalyconfig_controller_test.go">

<violation number="1" location="internal/controller/operator/vmanomalyconfig_controller_test.go:47">
P2: Fail fast on non-NotFound errors in test setup instead of silently ignoring them.</violation>
</file>

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

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

This entry is missing the mandatory issue/PR reference link required by the changelog structure.</violation>

<violation number="2" location="docs/CHANGELOG.md:223">
P2: This changelog entry is duplicated and appears in the wrong release section (`v0.64.0` and `v0.65.0`), which makes release notes inaccurate.</violation>

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

New changelog entries must be added only to `tip`; this line adds a new BUGFIX entry in a released section, which violates placement requirements.</violation>
</file>

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

<violation number="1" location="internal/controller/operator/vmanomalyconfig_controller.go:118">
P2: Propagate the CreateOrUpdateConfig error so reconcile fails and requeues instead of silently succeeding.</violation>
</file>

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

<violation number="1" location="internal/controller/operator/factory/vmanomaly/config/config.go:288">
P1: Writing merged model entries into `c.Models` can panic when the base config omits `models` (nil map). Initialize the map before assignment.</violation>

<violation number="2" location="internal/controller/operator/factory/vmanomaly/config/config.go:292">
P1: Writing merged scheduler entries into `c.Schedulers` can panic when the base config omits `schedulers` (nil map). Initialize the map before assignment.</violation>
</file>

<file name="internal/controller/operator/factory/vmanomaly/config/config_test.go">

<violation number="1" location="internal/controller/operator/factory/vmanomaly/config/config_test.go:714">
P2: The new external-config test sets `ConfigNamespaceSelector` but doesn't create a matching labeled Namespace object, so no `VMAnomalyConfig` can be selected in this setup.</violation>
</file>

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

cubic-dev-ai · 2026-04-02T15:20:31Z

+		BeforeEach(func() {
+			By("creating the custom resource for the Kind VMAnomalyConfig")
+			err := k8sClient.Get(ctx, typeNamespacedName, vmanomalyconfig)
+			if err != nil && k8serrors.IsNotFound(err) {


P2: Fail fast on non-NotFound errors in test setup instead of silently ignoring them.

Prompt for AI agents

Check if this issue is valid — if so, understand the root cause and fix it. At internal/controller/operator/vmanomalyconfig_controller_test.go, line 47: <comment>Fail fast on non-NotFound errors in test setup instead of silently ignoring them.</comment> <file context> @@ -0,0 +1,83 @@ + BeforeEach(func() { + By("creating the custom resource for the Kind VMAnomalyConfig") + err := k8sClient.Get(ctx, typeNamespacedName, vmanomalyconfig) + if err != nil && k8serrors.IsNotFound(err) { + resource := &vmv1.VMAnomalyConfig{ + ObjectMeta: metav1.ObjectMeta{ </file context>

cubic-dev-ai · 2026-04-02T15:20:31Z

+			}
+		}
+
+		if err := vmanomaly.CreateOrUpdateConfig(ctx, r, item, &instance); err != nil {


P2: Propagate the CreateOrUpdateConfig error so reconcile fails and requeues instead of silently succeeding.

Prompt for AI agents

Check if this issue is valid — if so, understand the root cause and fix it. At internal/controller/operator/vmanomalyconfig_controller.go, line 118: <comment>Propagate the CreateOrUpdateConfig error so reconcile fails and requeues instead of silently succeeding.</comment> <file context> @@ -0,0 +1,136 @@ + } + } + + if err := vmanomaly.CreateOrUpdateConfig(ctx, r, item, &instance); err != nil { + l.Error(err, "failed to update vmanomaly config") + } </file context>

Copilot

Pull request overview

Copilot reviewed 31 out of 31 changed files in this pull request and generated 7 comments.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Copilot · 2026-04-03T13:02:28Z

+	parentObject := fmt.Sprintf("%s.%s.vmanomaly", cr.Name, cr.Namespace)
+	return reconcile.StatusForChildObjects(ctx, rclient, parentObject, []*vmv1.VMAnomalyConfig{childObject})


UpdateStatusesForChildObjects updates status using the childObject pointer passed by the caller. Since ParsedObjects.selectConfigs builds its own object instances, validation errors recorded via ChildObjects.ForEachCollectSkipInvalid won't be reflected in this childObject, so the condition may be marked applied even when this config was rejected (collision/unmarshal/etc). Consider looking up the matching object via pos.configs.Get(childObject) (and skipping update if it isn't selected) or updating statuses for pos.configs.All() when appropriate.

Suggested change

parentObject := fmt.Sprintf("%s.%s.vmanomaly", cr.Name, cr.Namespace)

return reconcile.StatusForChildObjects(ctx, rclient, parentObject, []*vmv1.VMAnomalyConfig{childObject})

selectedChildObject := pos.configs.Get(childObject)

if selectedChildObject == nil {

return nil

}

parentObject := fmt.Sprintf("%s.%s.vmanomaly", cr.Name, cr.Namespace)

return reconcile.StatusForChildObjects(ctx, rclient, parentObject, []*vmv1.VMAnomalyConfig{selectedChildObject})

Copilot · 2026-04-03T13:02:29Z

+func (r *VMAnomalyConfigReconciler) SetupWithManager(mgr ctrl.Manager) error {
+	return ctrl.NewControllerManagedBy(mgr).
+		For(&vmv1.VMAnomalyConfig{}).
+		WithEventFilter(predicate.TypedGenerationChangedPredicate[client.Object]{}).
+		WithOptions(getDefaultOptions()).
+		Complete(r)


SetupWithManager uses GenerationChangedPredicate, but this controller's Reconcile() contains deletion-specific behavior based on DeletionTimestamp. DeletionTimestamp updates do not change generation, so the reconcile that should remove the config from VMAnomaly instances may never run. Use a predicate that allows DeletionTimestamp/resourceVersion changes (or add a finalizer and react to the finalizer update) so delete flows are handled before the object disappears.

Copilot · 2026-04-03T13:02:29Z

+		if err := vmanomaly.CreateOrUpdateConfig(ctx, r, item, &instance); err != nil {
+			l.Error(err, "failed to update vmanomaly config")
+		}
+	}


Errors from vmanomaly.CreateOrUpdateConfig are only logged and then ignored, so the reconcile returns success even if updating VMAnomaly instances fails (no retry/requeue). Consider aggregating these errors (or returning the first error) so controller-runtime will requeue and the failure is visible.

Copilot · 2026-04-03T13:02:29Z

+The `VMAnomalyConfig` CRD allows to declaratively define anomaly detection [models](https://docs.victoriametrics.com/anomaly-detection/components/models/). [schedulers](https://docs.victoriametrics.com/anomaly-detection/components/schedulers/) and [queries](https://docs.victoriametrics.com/anomaly-detection/components/reader/#per-query-parameters).
+
+`VMAnomalyConfig` object updates `models`, `schedulers` and `reader.queries` sections of [VMAnomaly](https://docs.victoriametrics.com/anomaly-detection/)
+configuration by adding items with `{metadata.namespace}-{metadata.name}` key prefix. Whole VMAnomalyConfig fails if at least one item collides:


The doc claims "Whole VMAnomalyConfig fails if at least one item collides", but the current implementation uses ChildObjects.ForEachCollectSkipInvalid (skips invalid configs and continues generating the main config). Either adjust the implementation to fail hard on collisions, or update the documentation to reflect the skip-with-status behavior so users know what to expect.

Suggested change

configuration by adding items with `{metadata.namespace}-{metadata.name}` key prefix. Whole VMAnomalyConfig fails if at least one item collides:

configuration by adding items with `{metadata.namespace}-{metadata.name}` key prefix. If at least one generated item collides with an existing key, only the colliding item is skipped, while other valid items from the same `VMAnomalyConfig` are still added to the resulting configuration. Check the `VMAnomalyConfig` status and related events to identify skipped items caused by collisions.

Copilot · 2026-04-03T13:02:29Z

+	"context"
+
+	. "github.com/onsi/ginkgo/v2"
+	. "github.com/onsi/gomega"
+	k8serrors "k8s.io/apimachinery/pkg/api/errors"
+	metav1 "k8s.io/apimachinery/pkg/apis/meta/v1"
+	"k8s.io/apimachinery/pkg/types"
+	"sigs.k8s.io/controller-runtime/pkg/reconcile"
+
+	vmv1 "github.com/VictoriaMetrics/operator/api/operator/v1"
+)
+
+var _ = Describe("VMAnomalyConfig Controller", func() {
+	Context("When reconciling a resource", func() {
+		const resourceName = "test-resource"
+
+		ctx := context.Background()
+
+		typeNamespacedName := types.NamespacedName{
+			Name:      resourceName,
+			Namespace: "default", // TODO(user):Modify as needed
+		}
+		vmanomalyconfig := &vmv1.VMAnomalyConfig{}
+
+		BeforeEach(func() {
+			By("creating the custom resource for the Kind VMAnomalyConfig")
+			err := k8sClient.Get(ctx, typeNamespacedName, vmanomalyconfig)
+			if err != nil && k8serrors.IsNotFound(err) {
+				resource := &vmv1.VMAnomalyConfig{
+					ObjectMeta: metav1.ObjectMeta{
+						Name:      resourceName,
+						Namespace: "default",
+					},
+					// TODO(user): Specify other spec details if needed.
+				}
+				Expect(k8sClient.Create(ctx, resource)).To(Succeed())
+			}
+		})
+
+		AfterEach(func() {
+			// TODO(user): Cleanup logic after each test, like removing the resource instance.
+			resource := &vmv1.VMAnomalyConfig{}
+			err := k8sClient.Get(ctx, typeNamespacedName, resource)
+			Expect(err).NotTo(HaveOccurred())
+
+			By("Cleanup the specific resource instance VMAnomalyConfig")
+			Expect(k8sClient.Delete(ctx, resource)).To(Succeed())
+		})
+		It("should successfully reconcile the resource", func() {
+			By("Reconciling the created resource")
+			controllerReconciler := &VMAnomalyConfigReconciler{
+				Client:       k8sClient,
+				OriginScheme: k8sClient.Scheme(),
+			}
+
+			_, err := controllerReconciler.Reconcile(ctx, reconcile.Request{
+				NamespacedName: typeNamespacedName,
+			})
+			Expect(err).NotTo(HaveOccurred())
+			// TODO(user): Add more specific assertions depending on your controller's reconciliation logic.
+			// Example: If you expect a certain status condition after reconciliation, verify it here.
+		})
+	})
+})


This new controller test is kubebuilder scaffold with TODOs and no assertions about reconciliation side-effects, so it doesn't meaningfully cover the new behavior. Either implement real assertions (e.g., create VMAnomaly + VMAnomalyConfig and verify the generated Secret/status updates), or remove the scaffold test to avoid giving a false sense of coverage.

Suggested change

"context"

. "github.com/onsi/ginkgo/v2"

. "github.com/onsi/gomega"

k8serrors "k8s.io/apimachinery/pkg/api/errors"

metav1 "k8s.io/apimachinery/pkg/apis/meta/v1"

"k8s.io/apimachinery/pkg/types"

"sigs.k8s.io/controller-runtime/pkg/reconcile"

vmv1 "github.com/VictoriaMetrics/operator/api/operator/v1"

)

var _ = Describe("VMAnomalyConfig Controller", func() {

Context("When reconciling a resource", func() {

const resourceName = "test-resource"

ctx := context.Background()

typeNamespacedName := types.NamespacedName{

Name: resourceName,

Namespace: "default", // TODO(user):Modify as needed

}

vmanomalyconfig := &vmv1.VMAnomalyConfig{}

BeforeEach(func() {

By("creating the custom resource for the Kind VMAnomalyConfig")

err := k8sClient.Get(ctx, typeNamespacedName, vmanomalyconfig)

if err != nil && k8serrors.IsNotFound(err) {

resource := &vmv1.VMAnomalyConfig{

ObjectMeta: metav1.ObjectMeta{

Name: resourceName,

Namespace: "default",

},

// TODO(user): Specify other spec details if needed.

}

Expect(k8sClient.Create(ctx, resource)).To(Succeed())

}

})

AfterEach(func() {

// TODO(user): Cleanup logic after each test, like removing the resource instance.

resource := &vmv1.VMAnomalyConfig{}

err := k8sClient.Get(ctx, typeNamespacedName, resource)

Expect(err).NotTo(HaveOccurred())

By("Cleanup the specific resource instance VMAnomalyConfig")

Expect(k8sClient.Delete(ctx, resource)).To(Succeed())

})

It("should successfully reconcile the resource", func() {

By("Reconciling the created resource")

controllerReconciler := &VMAnomalyConfigReconciler{

Client: k8sClient,

OriginScheme: k8sClient.Scheme(),

}

_, err := controllerReconciler.Reconcile(ctx, reconcile.Request{

NamespacedName: typeNamespacedName,

})

Expect(err).NotTo(HaveOccurred())

// TODO(user): Add more specific assertions depending on your controller's reconciliation logic.

// Example: If you expect a certain status condition after reconciliation, verify it here.

})

})

})

. "github.com/onsi/ginkgo/v2"

)

// The autogenerated kubebuilder scaffold test for VMAnomalyConfig was removed

// because it only asserted that Reconcile returned no error and did not verify

// any reconciliation side-effects. Add a controller test here once concrete

// assertions can be made against observable behavior.

cubic-dev-ai

1 issue found across 2 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:20">
P1: Custom agent: **Changelog Review Agent**

This new changelog item is non-compliant with the required changelog format: it is missing the mandatory `FEATURE|BUGFIX|SECURITY` prefix, affected services, and reference links.</violation>
</file>

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

vrutkovs · 2026-04-17T06:57:01Z

Do we want to run it through v1beta1 for a few releases first?

vrutkovs · 2026-04-17T07:18:22Z

+		for i := range list.Items {
+			item := &list.Items[i]


Suggested change

for i := range list.Items {

item := &list.Items[i]

for _, item := range list.Items {

Since we're not mutating item here

we're mutating them later in ForEach loops

vrutkovs · 2026-04-17T07:21:06Z

+	case cr.Spec.ConfigRawYaml != "":
+		data = []byte(cr.Spec.ConfigRawYaml)
+	default:
+		return nil, fmt.Errorf(`either "configRawYaml" or "configSecret" are required`)


We should do this check via validatingwebhook. Also, I'd expect raw yaml to take precedence when both are specified?

vmalertmanager has the same properties and priorities are the same

vrutkovs · 2026-04-17T08:13:39Z

 )

+func reloadSupported(cr *vmv1.VMAnomaly) bool {
+	anomalyVersion, err := semver.NewVersion(cr.Spec.Image.Tag)


This might break if customers use custom tags / RCs - we should add a CHANGELOG entry for this

rcs should be covered by this check, but custom builds - not, haven't seen Fred shares builds with nonstandard versions

Okay, lets mention it in the changelog - there is a chance the customers may mirror the images in their org and having this mentioned may save us some time on issue troubleshooting

vrutkovs · 2026-04-17T08:21:11Z

+		}
+
+		if err := vmanomaly.CreateOrUpdateConfig(ctx, r, item, &instance); err != nil {
+			l.Error(err, "failed to update vmanomaly config")


Suggested change

l.Error(err, "failed to update vmanomaly config")

l.Error(err, "failed to update vmanomaly config")

return

problem with this change is that error can be caused by other vmanomalyconfig

vrutkovs · 2026-04-17T08:29:17Z

+						Name:      resourceName,
+						Namespace: "default",
+					},
+					// TODO(user): Specify other spec details if needed.


this is autogenerated file

vrutkovs · 2026-04-17T08:30:55Z

+				NamespacedName: typeNamespacedName,
+			})
+			Expect(err).NotTo(HaveOccurred())
+			// TODO(user): Add more specific assertions depending on your controller's reconciliation logic.


We can extend the e2e tests later

Co-authored-by: Vadim Rutkovsky <vadim@vrutkovs.eu> Signed-off-by: Andrii Chubatiuk <andrew.chubatiuk@gmail.com>

cubic-dev-ai

1 issue found across 2 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:22">
P3: Use a plural verb in this release note sentence ("were introduced" instead of "was introduced").</violation>
</file>

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

Co-authored-by: Vadim Rutkovsky <vadim@vrutkovs.eu> Signed-off-by: Andrii Chubatiuk <andrew.chubatiuk@gmail.com>

Signed-off-by: Vadim Rutkovsky <vadim@vrutkovs.eu>

Co-authored-by: Vadim Rutkovsky <vadim@vrutkovs.eu> Signed-off-by: Andrii Chubatiuk <andrew.chubatiuk@gmail.com>

AndrewChubatiuk requested review from Haleygo and f41gh7 as code owners July 17, 2025 08:33

AndrewChubatiuk marked this pull request as draft July 17, 2025 08:34

AndrewChubatiuk force-pushed the introduce-vmanomalymodel branch 2 times, most recently from 7b569bb to a7fc951 Compare July 17, 2025 09:39

AndrewChubatiuk marked this pull request as ready for review July 17, 2025 09:39

AndrewChubatiuk requested a review from zekker6 July 17, 2025 09:39

AndrewChubatiuk force-pushed the introduce-vmanomalymodel branch 3 times, most recently from 840964f to 9e5ab0f Compare July 17, 2025 10:47

f41gh7 previously requested changes Jul 18, 2025

View reviewed changes

AndrewChubatiuk force-pushed the introduce-vmanomalymodel branch from 0ec9f87 to 1ba5e13 Compare July 18, 2025 12:20

AndrewChubatiuk force-pushed the introduce-vmanomalymodel branch from 1ba5e13 to 4558e7c Compare July 29, 2025 13:19

AndrewChubatiuk changed the title ~~introduce VMAnomalyModel~~ introduce VMAnomalyModel and VMAnomalyScheduler Jul 29, 2025

AndrewChubatiuk force-pushed the introduce-vmanomalymodel branch 5 times, most recently from 1b8eb91 to 2216f0a Compare July 29, 2025 14:58

AndrewChubatiuk force-pushed the introduce-vmanomalymodel branch from 2216f0a to d0a06c0 Compare September 11, 2025 08:37

AndrewChubatiuk force-pushed the introduce-vmanomalymodel branch 2 times, most recently from 66eac73 to bfc5203 Compare October 7, 2025 08:05

AndrewChubatiuk requested a review from f41gh7 October 17, 2025 18:51

AndrewChubatiuk force-pushed the introduce-vmanomalymodel branch 5 times, most recently from cdea53b to 5914c18 Compare October 21, 2025 13:33

AndrewChubatiuk force-pushed the introduce-vmanomalymodel branch from 30c4e13 to 96dc1df Compare January 10, 2026 11:39

AndrewChubatiuk requested a review from Copilot January 10, 2026 11:40

Copilot started reviewing on behalf of AndrewChubatiuk January 10, 2026 11:41 View session

This comment was marked as outdated.

Sign in to view

AndrewChubatiuk force-pushed the introduce-vmanomalymodel branch from 96dc1df to 9d58b90 Compare January 10, 2026 11:47

AndrewChubatiuk requested a review from Copilot January 10, 2026 11:48

Copilot started reviewing on behalf of AndrewChubatiuk January 10, 2026 11:50 View session

Copilot AI reviewed Jan 10, 2026

View reviewed changes

AndrewChubatiuk removed request for Haleygo and f41gh7 January 12, 2026 11:54

AndrewChubatiuk force-pushed the introduce-vmanomalymodel branch from 9d58b90 to 11c333c Compare January 14, 2026 17:05

AndrewChubatiuk force-pushed the introduce-vmanomalymodel branch from 11c333c to bf10354 Compare April 2, 2026 13:09

AndrewChubatiuk changed the title ~~introduce VMAnomalyModel and VMAnomalyScheduler~~ introduce VMAnomalyConfig Apr 2, 2026

AndrewChubatiuk force-pushed the introduce-vmanomalymodel branch from c53d6a0 to 21aa85c Compare April 2, 2026 15:15

cubic-dev-ai Bot reviewed Apr 2, 2026

View reviewed changes

Copilot AI reviewed Apr 3, 2026

View reviewed changes

cubic-dev-ai Bot reviewed Apr 8, 2026

View reviewed changes

Comment thread docs/CHANGELOG.md Outdated

AndrewChubatiuk and others added 4 commits April 13, 2026 14:29

introduce VMAnomalyModel and VMAnomalyScheduler

7b064ab

replace vmanomalymodel and vmanomalyscheduler with vmanomalyconfig

e595d8c

disabled upgrade tests for anomaly, command-line args change is expected

e709e9f

docs: update vmanomaly resources doc

419ad0b

vrutkovs requested changes Apr 17, 2026

View reviewed changes

AndrewChubatiuk and others added 2 commits April 17, 2026 11:50

Update test/e2e/upgrade/upgrade_test.go

e44ae44

Co-authored-by: Vadim Rutkovsky <vadim@vrutkovs.eu> Signed-off-by: Andrii Chubatiuk <andrew.chubatiuk@gmail.com>

Update docs/CHANGELOG.md

90e02c6

Co-authored-by: Vadim Rutkovsky <vadim@vrutkovs.eu> Signed-off-by: Andrii Chubatiuk <andrew.chubatiuk@gmail.com>

cubic-dev-ai Bot reviewed Apr 17, 2026

View reviewed changes

Comment thread docs/CHANGELOG.md Outdated

Update internal/controller/operator/factory/vmanomaly/pod.go

2ba075a

Co-authored-by: Vadim Rutkovsky <vadim@vrutkovs.eu> Signed-off-by: Andrii Chubatiuk <andrew.chubatiuk@gmail.com>

vrutkovs approved these changes Apr 17, 2026

View reviewed changes

Merge branch 'master' into introduce-vmanomalymodel

bafa619

Signed-off-by: Vadim Rutkovsky <vadim@vrutkovs.eu>

vrutkovs reviewed Apr 17, 2026

View reviewed changes

Comment thread docs/resources/vmanomaly.md Outdated

Update docs/resources/vmanomaly.md

24b8bbb

Co-authored-by: Vadim Rutkovsky <vadim@vrutkovs.eu> Signed-off-by: Andrii Chubatiuk <andrew.chubatiuk@gmail.com>

		parentObject := fmt.Sprintf("%s.%s.vmanomaly", cr.Name, cr.Namespace)
		return reconcile.StatusForChildObjects(ctx, rclient, parentObject, []*vmv1.VMAnomalyConfig{childObject})

	configuration by adding items with `{metadata.namespace}-{metadata.name}` key prefix. Whole VMAnomalyConfig fails if at least one item collides:
	configuration by adding items with `{metadata.namespace}-{metadata.name}` key prefix. If at least one generated item collides with an existing key, only the colliding item is skipped, while other valid items from the same `VMAnomalyConfig` are still added to the resulting configuration. Check the `VMAnomalyConfig` status and related events to identify skipped items caused by collisions.

	for i := range list.Items {
	item := &list.Items[i]
	for _, item := range list.Items {

	l.Error(err, "failed to update vmanomaly config")
	l.Error(err, "failed to update vmanomaly config")
	return

Conversation

AndrewChubatiuk commented Jul 17, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

f41gh7 left a comment

Choose a reason for hiding this comment

Uh oh!

AndrewChubatiuk commented Jul 18, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

AndrewChubatiuk commented Jul 29, 2025

Uh oh!

This comment was marked as outdated.

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Uh oh!

cubic-dev-ai Bot left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

cubic-dev-ai Bot Apr 2, 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 Apr 2, 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!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Uh oh!

Uh oh!

Copilot AI Apr 3, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Apr 3, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Apr 3, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Apr 3, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Apr 3, 2026

Choose a reason for hiding this comment

Uh oh!

Uh oh!

cubic-dev-ai Bot left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

AndrewChubatiuk commented Jul 17, 2025 •

edited

Loading

AndrewChubatiuk commented Jul 18, 2025 •

edited

Loading

cubic-dev-ai Bot Apr 2, 2026 •

edited

Loading

cubic-dev-ai Bot Apr 2, 2026 •

edited

Loading