Clean up deployment's helm files

[jeandemeusy]

Cleaned-up the deployment files.
The common values between staging and production have been set as such. Specific staging parameter also, except for some secrets that needs to be done.
Also changed the tag structure to be next to replicaCount and envParameters for each module.

Summary by CodeRabbit

• New Features

  • Enhanced core configurations including health checks, subgraph operations, and economic models.
  • Improved node operations settings for better channel management and peer interactions.
  • New environment variables for message handling efficiency in Postman component.

• Enhancements

  • Updated Kubernetes deployment configurations for core and Postman containers to use refined image repository references.
  • Simplified the structure of configuration files by restructuring image properties.

• Bug Fixes

  • Adjusted environment variables and settings in production configurations to align with operational requirements.

• Documentation

  • Updated comments and documentation in configuration files to reflect recent changes and additions.

[coderabbitai]

Walkthrough

Walkthrough

The updates across various Helm configuration files for ctdapp mainly involve adding new configurations and environment variables, restructuring existing ones, and updating image references. These changes enhance core functionalities, improve node operations, and refine the deployment process for both production and staging environments.

Changes

Files	Change Summary
helm/ctdapp/templates/configmap-core.yaml, helm/ctdapp/templates/configmap-postman.yaml	Added various new configurations and environment variables related to core functionalities, node operations, distribution settings, peer versions, GCP configurations, economic models, and RabbitMQ details.
helm/ctdapp/templates/deployment-core.yaml, helm/ctdapp/templates/deployment-postman.yaml	Updated image repository and pull policy references for core and Postman containers in Kubernetes deployment configurations.
helm/ctdapp/values.yaml, helm/values-prod.yaml	Restructured image properties by moving them directly under core and postman, adjusted environment variables for core components, and modified values like DISTRIBUTION_MIN_ELIGIBLE_PEERS, DISTRIBUTION_MAX_APR_PERCENTAGE, GCP_BUCKET, and CHANNEL_MIN_BALANCE.
helm/secrets-staging.sops.yaml	Updated subgraph section with new comments and modifications to URL values like safesBalanceUrl, stakingUrl, and wxhoprTxsUrl, along with updating lastmodified and mac values.

🐇✨
In the land of code and helm,
A rabbit hopped with a new realm.
Flags and vars, in files they dwell,
Changes made, with tales to tell.
Hop, skip, deploy, all's well! 🌟
🐇✨

---

Recent Review Details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 97cc97b and 102497c.

Files selected for processing (1)

• helm/ctdapp/values.yaml (1 hunks)

Files skipped from review due to trivial changes (1)

• helm/ctdapp/values.yaml

---

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>.
  • 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 generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @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.

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 as PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger a review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration 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.