Skip to content

VMAgent/VMAnomaly: set default spec.shardCount - #2475

Merged
vrutkovs merged 2 commits into
masterfrom
set-shard-count-to-1
Aug 6, 2026
Merged

VMAgent/VMAnomaly: set default spec.shardCount#2475
vrutkovs merged 2 commits into
masterfrom
set-shard-count-to-1

Conversation

@AndrewChubatiuk

Copy link
Copy Markdown
Contributor

fixes #2473

@cubic-dev-ai cubic-dev-ai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

All reported issues were addressed across 7 files

Reply with feedback, questions, or to request a fix.

Fix all with cubic | Re-trigger cubic

Comment thread docs/CHANGELOG.md Outdated
Comment thread api/operator/v1/vmanomaly_types.go Outdated
@AndrewChubatiuk
AndrewChubatiuk force-pushed the set-shard-count-to-1 branch 2 times, most recently from f94000e to 198718d Compare August 6, 2026 09:35
@AndrewChubatiuk AndrewChubatiuk changed the title set spec.shardCount to 1 by default VMAgent/VMAnomaly: set default spec.shardCount Aug 6, 2026
@vrutkovs
vrutkovs enabled auto-merge (squash) August 6, 2026 11:16
@vrutkovs
vrutkovs merged commit 4797937 into master Aug 6, 2026
9 checks passed
@vrutkovs
vrutkovs deleted the set-shard-count-to-1 branch August 6, 2026 12:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

VMAgent and VPA: fails when .spec.shardCount is unset

2 participants