ci: retry on error during installing operator

[WenyXu]

I hereby agree to the terms of the GreptimeDB CLA.

Refer to a related PR or issue link (optional)

What's changed and what's your intention?

Retry on error during installing operator

Checklist

• I have written the necessary rustdoc comments.
• I have added the necessary unit tests and integration tests.
• This PR requires documentation updates.

Summary by CodeRabbit

• Chores
  • Improved reliability of the GreptimeDB operator setup by adding a retry mechanism during installation.

[coderabbitai]

Walkthrough

The .github/actions/setup-greptimedb-cluster/action.yml file has been updated to incorporate a retry mechanism for installing the GreptimeDB operator. By utilizing the nick-fields/retry@v3 GitHub Action, the installation steps are now more robust against transient failures, encapsulated within a retry logic configuration.

Changes

Files	Change Summary
.github/actions/setup-greptimedb-cluster/action.yml	Replaced the installation steps for the GreptimeDB operator with a retry mechanism using the nick-fields/retry@v3 action.

Poem

In the meadow, we code with glee,
GreptimeDB installs beautifully.
With retries in place, we stand in cheer,
No transient failures shall we fear.
CodeRabbit bounds with joyful might,
Making installations smooth and bright. 🌟

---

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.
  • @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 as 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.

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.

[coderabbitai]

Actionable comments posted: 0

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 8a119aa and e48b14d.

Files selected for processing (1)

• .github/actions/setup-greptimedb-cluster/action.yml (1 hunks)

Additional comments not posted (5)

.github/actions/setup-greptimedb-cluster/action.yml (5)

34-49: LGTM! The retry mechanism is correctly implemented.

The retry mechanism using nick-fields/retry@v3 is correctly configured with appropriate parameters. The encapsulated shell script for installing the GreptimeDB operator is also correct.

---

Line range hint 50-70:
Ensure compatibility with the retry mechanism.

The installation steps for the GreptimeDB cluster look correct. However, consider adding a retry mechanism for this step as well to ensure robustness.

---

Line range hint 71-83:
Efficient waiting mechanism.

The loop correctly waits for the GreptimeDB cluster to be ready by checking the cluster phase every 5 seconds and printing the current phase and pod status.

---

Line range hint 84-88:
Useful debugging step.

The step to print all resources in the GreptimeDB namespace with their labels is useful for debugging and ensuring the cluster is correctly set up.

---

Line range hint 89-93:
Useful debugging step.

The step to describe the nodes in the Kubernetes cluster is useful for debugging and ensuring the nodes are correctly configured.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 85.02%. Comparing base (849e0b9) to head (e48b14d).
Report is 4 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #4295      +/-   ##
==========================================
- Coverage   85.31%   85.02%   -0.29%     
==========================================
  Files        1063     1063              
  Lines      188345   188508     +163     
==========================================
- Hits       160686   160285     -401     
- Misses      27659    28223     +564