fix: Bump otel limits

[zacharyblasczyk]

Summary by CodeRabbit

• Chores
  • Component Upgrade: Updated a core component to a new version, bolstering system stability and ensuring seamless integration with future enhancements.
  • Resource Optimization: Increased CPU and memory limits to better support intensive workloads, leading to smoother operations and improved responsiveness.
  • Overall Impact: These behind‐the-scenes improvements optimize resource utilization and contribute to a more reliable experience during peak usage.

[coderabbitai]

Walkthrough

The pull request updates configurations in two files. In the Helm chart’s Chart.yaml, the version is bumped from 0.26.8 to 0.26.9. In the agent values file, the CPU and memory resource limits are increased from 500m/500Mi to 1000m/1000Mi. These modifications adjust deployment parameters in the operator-wandb chart without altering any functional logic.

Changes

File(s)	Change Summary
charts/operator-wandb/Chart.yaml	Updated version field from 0.26.8 to 0.26.9
charts/operator-wandb/.../agent/values.yaml	Increased resource limits: CPU from 500m to 1000m and memory from 500Mi to 1000Mi

Possibly related PRs

• fix: Bad template #351: Involved a similar version number update in Chart.yaml, indicating a related focus on chart metadata adjustments.

Suggested reviewers

• vanpelt
• jsbroks

Poem

I'm a code rabbit, hoppin' down the lane,
Upgraded versions, making code gains.
YAML fields blossomed with resource might,
CPU and memory soar to new height.
With a twitch of my nose, I cheer in delight!
🥕🐇 Happy code days, all day and night!

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 256bd42 and 8c37fff.

📒 Files selected for processing (2)

• charts/operator-wandb/Chart.yaml (1 hunks)
• charts/operator-wandb/charts/otel/charts/agent/values.yaml (1 hunks)

✅ Files skipped from review due to trivial changes (1)

• charts/operator-wandb/Chart.yaml

⏰ Context from checks skipped due to timeout of 90000ms (3)

• GitHub Check: Test Chart (v1.30.8, default)
• GitHub Check: Test Chart (v1.31.4, default)
• GitHub Check: Test Chart (v1.32.1, default)

🔇 Additional comments (1)

charts/operator-wandb/charts/otel/charts/agent/values.yaml (1)

79-80: Resource Limits Increase Approved

The updated resource limits (CPU: 1000m and memory: 1000Mi) are correctly implemented as per the PR objectives. These changes should provide additional headroom for the otel agent. However, note that the title indicates a bump in both limits and requests. Since the resource requests (lines 75–77) remain unchanged at cpu: 200m and memory: 200Mi, please verify that this was intentional and that the deployment’s scheduling or performance requirements are met.

---

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

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)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.