Skip to content

[zxp-netmon] fix helm chart repo name#240

Merged
dray92 merged 2 commits intomainfrom
debo/fix_helm
Jan 10, 2026
Merged

[zxp-netmon] fix helm chart repo name#240
dray92 merged 2 commits intomainfrom
debo/fix_helm

Conversation

@dray92
Copy link
Contributor

@dray92 dray92 commented Jan 10, 2026

[Title]

📚 Description of Changes

Provide an overview of your changes and why they’re needed. Link to any related issues (e.g., "Fixes #123"). If your PR fixes a bug, resolves a feature request, or updates documentation, please explain how.

  • What Changed:
    (Describe the modifications, additions, or removals.)

  • Why This Change:
    (Explain the problem this PR addresses or the improvement it provides.)

  • Affected Components:
    (Which component does this change affect? - put x for all components)

  • Compose

  • K8s

  • Other (please specify)

❓ Motivation and Context

Why is this change required? What problem does it solve?

  • Context:
    (Provide background information or link to related discussions/issues.)

  • Relevant Tasks/Issues:
    (e.g., Fixes: #GitHub Issue)

🔍 Types of Changes

Indicate which type of changes your code introduces (check all that apply):

  • BUGFIX: Non-breaking fix for an issue.
  • NEW FEATURE: Non-breaking addition of functionality.
  • BREAKING CHANGE: Fix or feature that causes existing functionality to not work as expected.
  • ENHANCEMENT: Improvement to existing functionality.
  • CHORE: Changes that do not affect production (e.g., documentation, build tooling, CI).

🔬 QA / Verification Steps

Describe the steps a reviewer should take to verify your changes:

  1. (Step one: e.g., "Run make test to verify all tests pass.")
  2. (Step two: e.g., "Deploy to a Kind cluster with make create-kind && make deploy.")
  3. (Additional steps as needed.)

✅ Global Checklist

Please check all boxes that apply:

  • I have read and followed the CONTRIBUTING guidelines.
  • My code follows the code style of this project.
  • I have updated the documentation as needed.
  • I have added tests that cover my changes.
  • All new and existing tests have passed locally.
  • I have run this code in a local environment to verify functionality.
  • I have considered the security implications of this change.

Summary by CodeRabbit

Release Notes

  • Chores
    • Container image repository moved to a new stable location and pinned to v0.0.52 for predictable deployments and consistent versioning.
  • Configuration
    • Default export interval increased from 5s to 60s, reducing export frequency and lowering operational load.

✏️ Tip: You can customize this high-level summary in your review settings.

@coderabbitai
Copy link

coderabbitai bot commented Jan 10, 2026

📝 Walkthrough

Walkthrough

Updated Helm chart values for zxporter-netmon: changed image.repository from devzero/zxporter-netmon to devzeroinc/zxporter-netmon, bumped image.tag from latest to v0.0.52, and increased config.exportInterval from 5s to 60s.

Changes

Cohort / File(s) Summary
Helm Configuration Update
helm-chart/zxporter-netmon/values.yaml
Changed image.repository to devzeroinc/zxporter-netmon; set image.tag to v0.0.52; updated config.exportInterval from 5s to 60s.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Suggested reviewers

  • Parthiba-Hazra
  • lbagic
  • sandipanpanda

Poem

🐰 A tiny bump, a tidy tweak,
Repo renamed, the tag unique.
Exports slower, steady pace,
Netmon hops to find its place. 🥕

🚥 Pre-merge checks | ✅ 3 | ❌ 2
❌ Failed checks (2 warnings)
Check name Status Explanation Resolution
Linked Issues check ⚠️ Warning The linked issue #123 is about cluster snapshot enum name fix, which is unrelated to the helm chart repository name, image tag, and export interval changes in this PR. Verify the correct linked issue is associated with this PR. The current linked issue does not match the helm chart configuration changes being made.
Out of Scope Changes check ⚠️ Warning The PR includes changes beyond the helm chart repo name fix: image tag pinning to v0.0.52 and export interval reduction to 60s, which appear out of scope relative to the PR title. Either update the PR title to reflect all changes (repo name, image tag, and export interval), or move the extra changes to separate PRs with appropriate documentation.
✅ Passed checks (3 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The PR title mentions fixing helm chart repo name, which aligns with the primary change (image.repository update from devzero to devzeroinc), though it omits the secondary changes to image tag and export interval.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.


📜 Recent review details

Configuration used: defaults

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 6a70371 and 3ce1dbf.

📒 Files selected for processing (1)
  • helm-chart/zxporter-netmon/values.yaml
🚧 Files skipped from review as they are similar to previous changes (1)
  • helm-chart/zxporter-netmon/values.yaml
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (3)
  • GitHub Check: Build Docker Image
  • GitHub Check: Build Docker Image
  • GitHub Check: Analyze (go)

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 and usage tips.

@dray92 dray92 enabled auto-merge (squash) January 10, 2026 02:05
@dray92 dray92 disabled auto-merge January 10, 2026 02:06
@dray92 dray92 enabled auto-merge (squash) January 10, 2026 02:08
@dray92 dray92 merged commit 659db62 into main Jan 10, 2026
26 checks passed
@dray92 dray92 deleted the debo/fix_helm branch January 10, 2026 02:18
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

Comments