chore: bump debug pod version to '20241107-9c210d18'

[daviderli614]

Add mysql and psql commands in the debug pod.

Summary by CodeRabbit

• New Features

  • Updated the debug pod image to a newer version.

• Documentation

  • Version updated in the README to reflect the new chart version.

• Chores

  • Incremented the Helm chart version from 0.2.31 to 0.2.32.
  • Commented out various configuration sections in the values file for future reference.

[coderabbitai]

Walkthrough

The pull request introduces updates to the greptimedb-cluster Helm chart, specifically incrementing the version from 0.2.31 to 0.2.32 in the Chart.yaml and README.md files. Additionally, the debug pod image tag has been updated from 20240905-67eaa147 to 20241107-9c210d18 in both the README.md and values.yaml files. Several sections in the values.yaml have been commented out, but the overall structure remains unchanged.

Changes

File Path	Change Summary
charts/greptimedb-cluster/Chart.yaml	Version updated from 0.2.31 to 0.2.32.
charts/greptimedb-cluster/README.md	Version updated from 0.2.31 to 0.2.32; debug pod image tag updated from 20240905-67eaa147 to 20241107-9c210d18.
charts/greptimedb-cluster/values.yaml	Debug pod image tag updated from 20240905-67eaa147 to 20241107-9c210d18; several sections commented out.

Possibly related PRs

• chore: bump greptimedb version from v0.9.0 to v0.9.1 #151: The changes involve a version bump in the Chart.yaml file for the greptimedb-cluster, similar to the version update in the main PR.
• chore: bump greptimedb version from v0.9.1 to v0.9.2 #158: This PR also updates the Chart.yaml file for the greptimedb-cluster, reflecting a version increment, which aligns with the version bump in the main PR.
• chore: bump greptimedb version from v0.9.3 to v0.9.4 #168: The version update in the Chart.yaml for the greptimedb-cluster is consistent with the version change in the main PR.
• chore: bump greptimedb version to v0.9.5 #175: This PR includes a version increment in the Chart.yaml for the greptimedb-cluster, matching the version update in the main PR.
• chore: update cluster dashboard #199: The version change in the Chart.yaml for the greptimedb-cluster aligns with the version bump in the main PR.

🐇 In the meadow, a version did rise,
From 0.2.31, to 0.2.32 flies!
With tags that do change, and pods that gleam,
Our Helm chart's ready, a developer's dream!
So hop along, let’s deploy with cheer,
For every small change, brings progress near! 🌼

Warning

Rate limit exceeded

@daviderli614 has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 15 minutes and 12 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

📥 Commits

Reviewing files that changed from the base of the PR and between 8d4d78f and 4ebd35c.

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between 8d4d78f and 4ebd35c.

📒 Files selected for processing (3)

• charts/greptimedb-cluster/Chart.yaml (1 hunks)
• charts/greptimedb-cluster/README.md (2 hunks)
• charts/greptimedb-cluster/values.yaml (1 hunks)

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

• charts/greptimedb-cluster/Chart.yaml
• charts/greptimedb-cluster/README.md
• charts/greptimedb-cluster/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>, 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.