ci: add build-operator-local-test-image and push-operator-local-test-image

[zyy17]

Summary by CodeRabbit

• New Features

  • Introduced a new target for building the operator binary specifically for Linux environments.
  • Added targets for building and pushing a local test Docker image of the operator.
  • Created a new Dockerfile for a containerized environment using Ubuntu 22.04 for the operator.

• Bug Fixes

  • Standardized the syntax for setting the PATH environment variable in Dockerfiles, improving consistency.

[coderabbitai]

Walkthrough

The changes introduced in this pull request enhance the build and deployment process for the greptimedb-operator. A new Makefile target for building the operator specifically for Linux environments has been added, along with targets for building and pushing a Docker image. Minor formatting adjustments were made to existing Dockerfiles for consistency, and a new Dockerfile was introduced to set up a containerized environment using Ubuntu 22.04, ensuring the operator can be executed directly within the container.

Changes

File	Change Summary
Makefile	Added build-for-linux, build-operator-local-test-image, and push-operator-local-test-image targets.
docker/initializer/Dockerfile	Reformatted ENV instruction for PATH variable (cosmetic change).
docker/operator/Dockerfile	Reformatted ENV instruction for PATH variable (cosmetic change).
docker/operator/Dockerfile.local	Introduced a new Dockerfile with Ubuntu 22.04, setting up the environment and entry point for the operator.

Sequence Diagram(s)

sequenceDiagram
    participant Developer
    participant Makefile
    participant Docker
    participant Container

    Developer->>Makefile: Run build-for-linux
    Makefile->>Docker: Build operator binary for Linux
    Makefile->>Docker: Build local test image
    Docker->>Container: Copy binary and set up environment
    Container->>Container: Set entry point to greptimedb-operator

Loading

Poem

🐇 In the garden of code, changes bloom,
New paths for the operator to zoom!
With Docker and Makefile, we build and we play,
A rabbit's delight in a tech-savvy way!
Hopping through Linux, so spry and so bright,
Our greptimedb-operator takes flight! 🌼

---

Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between b4c971c and 260dfbb.

Files selected for processing (4)

• Makefile (5 hunks)
• docker/initializer/Dockerfile (1 hunks)
• docker/operator/Dockerfile (1 hunks)
• docker/operator/Dockerfile.local (1 hunks)

Files skipped from review due to trivial changes (2)

• docker/initializer/Dockerfile
• docker/operator/Dockerfile

Additional comments not posted (6)

docker/operator/Dockerfile.local (1)

1-7: LGTM!

The Dockerfile follows best practices and sets up a clean and isolated environment for running the greptimedb-operator application. The use of Ubuntu 22.04 as the base image ensures that the application runs on a stable and well-supported platform. Copying the binary and setting it as the entry point makes it easy to deploy and run the application in a containerized environment.

Makefile (5)

23-26: LGTM!

The code segment correctly determines the system architecture and sets the ARCH variable accordingly. This allows the build process to be architecture-aware.

---

72-72: Looks good!

The formatting adjustment improves the alignment of the help command's output.

---

140-142: Excellent addition!

The new build-for-linux target facilitates building the operator binary for Linux environments. It correctly sets the GOARCH and GOOS environment variables to ensure compatibility.

---

168-172: Great work!

The new build-operator-local-test-image target enables building a Docker image for the operator using the locally built binary. It correctly handles copying the binary to the root directory, building the image, and cleaning up afterwards.

---

174-176: Looks good!

The new push-operator-local-test-image target enables pushing the locally built operator image to a registry. It correctly uses the IMAGE_REPO and IMAGE_TAG variables to determine the image repository and tag.

---

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

[daviderli614]

LGTM