Optimize workflows staging resources

[NicholasTurner23]

Description

Update staging celery and scheduler resources.

Summary by CodeRabbit

• New Features

  • Increased CPU resource limits for the scheduler and celery components to enhance performance.

• Bug Fixes

  • Adjusted resource limits to ensure optimal operation of critical components.

[coderabbitai]

Caution

Review failed

The pull request is closed.

📝 Walkthrough

Walkthrough

The changes made in this pull request involve updates to the resource limits for the scheduler and celery components in the Kubernetes configuration file values-stage.yaml. The CPU limits for both components have been increased from 1000m to 2000m, while memory limits remain unchanged at 2000Mi. Other resource requests for all components, including webserver, scheduler, celery, and redis, have not been modified, and the overall structure of the configuration file remains intact.

Changes

File	Change Summary
k8s/workflows/values-stage.yaml	Updated limits.cpu for scheduler and celery: 1000m → 2000m. Memory limits unchanged.

Possibly related PRs

• Update/implement celery k8s executor #3393: Modifies resource requests for the celery component in values-prod.yaml, related to CPU limits changes in values-stage.yaml.
• Update/implement celery k8s executor #3398: Similar updates to resource requests for the celery component in values-prod.yaml, indicating a connection to the main PR.
• Increase resources for Celery #3437: Focuses on increasing resources for Celery, aligning with changes made to the celery component's CPU limits.
• Update/implement celery k8s executor #3595: Directly addresses resource allocation for the celery component in values-stage.yaml, indicating a strong connection.

Suggested labels

ready for review

Suggested reviewers

• BenjaminSsempala
• Baalmart

🎉 In the land of Kubernetes, where resources play,
The scheduler and celery found a brighter day.
With CPU limits raised, they dance and they cheer,
As memory stays steady, there's nothing to fear!
So let’s celebrate this change, oh what a delight,
In the world of configs, everything feels right! 🎈

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 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 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.