Conversation
… Chart (#117) * Add memory and CPU request configurations for various services in Helm chart - Updated `questions.yml` to include `memoryRequest` and `cpuRequest` for services: web, space, admin, live, silo, monitor, api, worker, beatworker, and email_service. - Modified `values.yaml` to set default values for `memoryRequest` and `cpuRequest` for the aforementioned services. - Adjusted deployment templates to utilize the new request configurations for resource management. * Refactor email service resource configurations in Helm chart - Updated `questions.yml` to change variable names from `memory_limit` and `cpu_limit` to `memoryLimit` and `cpuLimit`. - Modified `values.yaml` to reflect the new variable names for memory and CPU limits and requests. - Adjusted `email.deployment.yaml` to utilize the updated variable names for resource requests and limits. * Refactor resource variable names in Helm chart - Updated `questions.yml` to change variable names from `memory_request`, `cpu_request`, `memory_limit`, and `cpu_limit` to `memoryRequest` and `cpuRequest`, `memoryLimit` and `cpuLimit`. - Modified `silo.deployment.yaml` to utilize the updated variable names for resource requests and limits. * Add memory and CPU request configurations for additional services in README.md - Updated the README.md to include `memoryRequest` and `cpuRequest` settings for services: web, space, admin, live, monitor, api, silo, worker, and beatworker. - Ensured consistency in documentation for resource management across all relevant services. * Update README.md to reflect new variable names for email service resource configurations - Changed variable names for memory and CPU limits and requests from `memory_limit`, `cpu_limit`, `memory_request`, and `cpu_request` to `memoryLimit`, `cpuLimit`, `memoryRequest`, and `cpuRequest` for the email service. - Ensured consistency with previous refactoring of resource variable names across the Helm chart.
…116) * Add resource request configurations for various components in Helm chart - Updated `questions.yml` to include memory and CPU request variables for web, space, admin, live, api, worker, and beatworker components. - Modified `values.yaml` to set default memory and CPU requests for each component. - Adjusted deployment templates to utilize the new request configurations for memory and CPU. * Bump Plane version to 1.1.2 in Chart.yaml * Add memory and CPU request configurations to README.md - Included `memoryRequest` and `cpuRequest` parameters for web, space, admin, live, api, worker, and beatworker components in the documentation. - Updated descriptions to clarify the purpose of these new parameters in the context of Kubernetes deployments. * Fix resource limits in space deployment template - Updated memory and CPU limit configurations in `space.deployment.yaml` to reference the correct `space` values instead of `web` values, ensuring accurate resource allocation for the space component. * Update image reference in space deployment template - Changed the image reference in `space.deployment.yaml` to use `space.image` instead of `space.images`, ensuring consistency with the updated configuration structure.
Contributor
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the You can disable this status message by setting the 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:
SupportNeed help? Create a ticket on our support page for assistance with any issues or questions. 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
Documentation and Community
|
akshat5302
changed the title
Plane EE:v1.2.4 and Plane CE:v1.1.2Plane-EE:v1.2.4 and Plane-CE:v1.1.2
This was referenced May 30, 2025
mguptahub
approved these changes
Jun 3, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.