Skip to content

chore: Updating victoria-metrics-operator - #326

Merged
jthakkar04 merged 1 commit into
mainfrom
jthakkar/updating-victoria-operator
Aug 12, 2026
Merged

chore: Updating victoria-metrics-operator#326
jthakkar04 merged 1 commit into
mainfrom
jthakkar/updating-victoria-operator

Conversation

@jthakkar04

@jthakkar04 jthakkar04 commented Aug 11, 2026

Copy link
Copy Markdown
Contributor

Summary by CodeRabbit

  • Chores
    • Updated the VictoriaMetrics Operator deployment to a newer release.
    • Enabled forced-conflict upgrades for VictoriaMetrics custom resource definitions during Helm deployments.

@jthakkar04
jthakkar04 requested a review from a team as a code owner August 11, 2026 20:03
@coderabbitai

coderabbitai Bot commented Aug 11, 2026

Copy link
Copy Markdown
Contributor

Review Change Stack

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 9392bcd5-b6e9-414e-ac23-d8feca5e1094

📥 Commits

Reviewing files that changed from the base of the PR and between 32abe3b and f32ad09.

⛔ Files ignored due to path filters (1)
  • deploy/operator/Chart.lock is excluded by !**/*.lock
📒 Files selected for processing (2)
  • deploy/operator/Chart.yaml
  • deploy/operator/values.yaml

📝 Walkthrough

Walkthrough

The Helm chart updates the Victoria Metrics operator dependency to version 0.66.3 and enables forced-conflict upgrades for Victoria Metrics CRDs.

Changes

Victoria Metrics operator chart

Layer / File(s) Summary
Operator dependency and CRD upgrade configuration
deploy/operator/Chart.yaml, deploy/operator/values.yaml
The chart dependency changes from 0.58.1 to 0.66.3. Helm CRD upgrades are enabled with forceConflicts: true.

Estimated code review effort: 2 (Simple) | ~5 minutes

Suggested reviewers: casey-coreweave

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title clearly identifies the main change: updating the Victoria Metrics operator dependency and configuration.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
✨ Finishing Touches 💡 1
🛠️ Fix failing CI checks 💡
  • Create stacked PR
  • Commit on current branch
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch jthakkar/updating-victoria-operator

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

upgrade:
enabled: true
# Required to update the Victoria CRD Fields
forceConflicts: true

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.

Did you run a test deployment with this?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

yes i did and i was able to pull up the grafana dashboards as well

@jthakkar04
jthakkar04 force-pushed the jthakkar/updating-victoria-operator branch from f32ad09 to fe61548 Compare August 12, 2026 17:36
@jthakkar04
jthakkar04 merged commit eb182a5 into main Aug 12, 2026
13 of 16 checks passed
@jthakkar04
jthakkar04 deleted the jthakkar/updating-victoria-operator branch August 12, 2026 17:56
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.

2 participants