fix: use v0.1.0 greptimedb-operator and greptimedb-initializer

[zyy17]

Summary by CodeRabbit

• New Features

  • Updated Helm charts for greptimedb-cluster and greptimedb-operator to versions 0.2.14 and 0.2.5, respectively.
  • Transitioned initializer and operator image tags from alpha to stable versions.

• Bug Fixes

  • Resolved potential issues by updating image tags to stable versions, enhancing reliability.

[coderabbitai]

Walkthrough

The pull request introduces version updates for the greptimedb-cluster and greptimedb-operator Helm charts. The version for greptimedb-cluster is incremented from 0.2.13 to 0.2.14, and the initializer image tag is updated from v0.1.0-alpha.29 to v0.1.0. Similarly, the greptimedb-operator version is updated from 0.2.4 to 0.2.5, with the image tag also changing from v0.1.0-alpha.29 to v0.1.0. These changes reflect a transition from alpha to stable versions without altering other configurations.

Changes

Files	Change Summary
charts/greptimedb-cluster/Chart.yaml	Version updated from 0.2.13 to 0.2.14.
charts/greptimedb-cluster/README.md	Version updated from 0.2.13 to 0.2.14; Initializer image tag changed from v0.1.0-alpha.29 to v0.1.0.
charts/greptimedb-cluster/values.yaml	Initializer tag updated from v0.1.0-alpha.29 to v0.1.0.
charts/greptimedb-operator/Chart.yaml	Version updated from 0.2.4 to 0.2.5.
charts/greptimedb-operator/README.md	Version updated from 0.2.4 to 0.2.5; Image tag changed from v0.1.0-alpha.29 to v0.1.0.
charts/greptimedb-operator/values.yaml	Image tag updated from v0.1.0-alpha.29 to v0.1.0.

Possibly related PRs

• chore: bump greptimedb-operator version #145: Involves a version bump for the greptimedb-operator, related to the overall versioning strategy of the GreptimeDB charts.
• chore: bump greptimedb version from v0.9.0 to v0.9.1 #151: Updates the version of the greptimedb-cluster chart, directly related to the versioning changes in the main PR.
• chore: bump greptimedb version from v0.9.1 to v0.9.2 #158: Also updates the greptimedb-cluster version, indicating similar versioning changes as seen in the main PR.
• chore: bump greptimedb version from v0.9.2 to v0.9.3 #164: Updates the greptimedb-cluster version, aligning with the version increment in the main PR.
• chore: bump greptimedb-operator to v0.1.0 #166: Updates the greptimedb-operator version, relevant to the versioning context of the main PR.

Suggested reviewers

• daviderli614

Poem

In the garden where the bunnies play,
New versions bloom, brightening the day.
From alpha to stable, we hop with glee,
Updating our charts, as happy as can be!
With tags that shine, and numbers that cheer,
Let's celebrate changes, for springtime is here! 🐇✨

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between 50638b1 and 899b9ed.

📒 Files selected for processing (6)

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

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

• charts/greptimedb-cluster/Chart.yaml
• charts/greptimedb-operator/Chart.yaml

🔇 Additional comments (7)

charts/greptimedb-operator/values.yaml (1)

11-11: Approved: Image tag updated to stable version.

The image tag has been updated from v0.1.0-alpha.29 to v0.1.0, which aligns with the PR title. This change represents a significant update from an alpha version to a stable release.

To ensure this change is intentional and compatible:

1. Verify that this version is the latest stable release:

2. Check for any breaking changes or important notes in the release:

3. Consider updating the project documentation to reflect this version change if necessary.

charts/greptimedb-operator/README.md (2)

5-5: Version bump looks good.

The chart version has been updated from 0.2.4 to 0.2.5, which is consistent with the changes made in this PR.

---

113-113: Verify the stability of the new image tag.

The image tag has been updated from "v0.1.0-alpha.29" to "v0.1.0", which represents a significant change from an alpha version to a stable release. This aligns with the PR objective of using v0.1.0 of greptimedb-operator.

Please confirm:

1. Has this stable version been thoroughly tested?
2. Are there any breaking changes or important updates that users should be aware of when upgrading from the alpha version?
3. Has the corresponding documentation been updated to reflect any changes in the stable version?

To verify the image tag change across the repository, you can run the following script:

charts/greptimedb-cluster/values.yaml (1)

17-17: LGTM! Verify compatibility with other components.

The update of the initializer image tag from v0.1.0-alpha.29 to v0.1.0 aligns with the PR objective. This change represents a move from an alpha (pre-release) version to a stable release, which is generally a positive improvement.

However, to ensure system stability:

1. Confirm that this version is compatible with other components in the GreptimeDB cluster.
2. Verify that any new features or changes in v0.1.0 are properly documented and understood.
3. Consider updating the documentation to reflect this version change, if necessary.

To verify the compatibility and usage of this new version, you can run the following script:

✅ Verification successful

Compatibility Verification Passed

No hardcoded references to v0.1.0-alpha.29 were found, and no compatibility issues related to the initializer image tag update were detected.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Check for any compatibility issues or usage of the old version

# Test 1: Check if there are any hardcoded references to the old version
echo "Checking for hardcoded references to v0.1.0-alpha.29:"
rg "v0.1.0-alpha.29" --type yaml --type markdown

# Test 2: Check for any potential compatibility issues mentioned in changelogs or release notes
echo "Checking for potential compatibility issues:"
rg -i "compatibility|breaking change|deprecat" --type markdown

Length of output: 442

charts/greptimedb-cluster/README.md (3)

5-5: Chart version updated

The chart version has been incremented from 0.2.13 to 0.2.14, which is appropriate for the changes made in this PR.

---

Line range hint 1-281: LGTM: Changes are consistent and appropriate

The updates to the chart version and initializer image tag are consistent with the PR objectives. No other parts of the file were modified, which maintains consistency in the rest of the documentation. The changes appear to be appropriate and don't introduce any obvious issues.

---

181-181: Initializer image tag updated to stable version

The initializer image tag has been updated from "v0.1.0-alpha.29" to "v0.1.0", indicating a move from an alpha release to a stable release. This change aligns with the PR title and objectives.

To ensure consistency, let's verify if there are any other references to the old alpha version in the repository:

---

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.