-
Notifications
You must be signed in to change notification settings - Fork 119
[monitoring] fix vpa for vmagent delete resources #820
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[monitoring] fix vpa for vmagent delete resources #820
Conversation
Signed-off-by: kklinch0 <kklinch0@gmail.com>
WalkthroughThe changes simplify the resource allocation configuration for the Changes
Sequence Diagram(s)sequenceDiagram
participant User
participant Kubernetes
participant vmagent
participant ConfigReloader
User->>Kubernetes: Apply vmagent.yaml
Kubernetes->>vmagent: Deploy with empty resources
Kubernetes->>ConfigReloader: Deploy with empty configReloaderResources
Possibly related PRs
Suggested reviewers
Poem
Tip ⚡💬 Agentic Chat (Pro Plan, General Availability)
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. 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
adc253a
to
4e9446d
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actionable comments posted: 0
🧹 Nitpick comments (1)
packages/system/monitoring-agents/templates/vmagent.yaml (1)
24-24
: Introduce emptyconfigReloaderResources
block
AddingconfigReloaderResources: {}
follows the same pattern for the config‑reloader sidecar. Consider documenting why it’s intentionally empty to aid future maintainers.
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (1)
packages/system/monitoring-agents/templates/vmagent.yaml
(1 hunks)
🔇 Additional comments (1)
packages/system/monitoring-agents/templates/vmagent.yaml (1)
23-23
: Empty resources to enable VPA-driven scaling
Replacing the previous hard‑coded CPU/memory requests and limits withresources: {}
is the right approach to let the Vertical Pod Autoscaler manage sizing automatically.Please verify that the VMAgent CRD accepts an empty
resources
block and that your VPA configuration targets the correct container. It’s recommended to test this in a staging environment and confirm that the VPA recommendations are applied as expected.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
<!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit - **Chores** - Updated resource allocation settings for monitoring agents by removing predefined CPU and memory limits. - Added an option to specify separate resource settings for the config reloader component. <!-- end of auto-generated comment: release notes by coderabbit.ai -->
Summary by CodeRabbit