Backport PR #2526 to release/v1.7 for [CI] Add workflow to synchronize ubuntu base image

[vdaas-ci]

Description

Sometimes we have docker rate limit issues when building locally.
When that problem occurs, I have implemented a way to build using ghcr's base image.

Related Issue

Versions

• Go Version: 1.22.3
• Rust Version: 1.77.2
• Docker Version: 20.10.8
• Kubernetes Version: v1.30.0
• NGT Version: 2.2.1

Checklist

• I have read the CONTRIBUTING document and completed our CLA agreement.
• I have checked open Pull Requests for the similar feature or fixes?

Special notes for your reviewer

Summary by CodeRabbit

• New Features

  • Integrated a new GitHub Actions workflow for building a "buildbase" Docker image.

• Chores

  • Updated Makefile and Makefile.d to support the new "buildbase" Docker image.
  • Added a Dockerfile for the "buildbase" image.

[cloudflare-workers-and-pages]

Deploying vald with    Cloudflare Pages

Latest commit:	8251050
Status:	✅  Deploy successful!
Preview URL:	https://53e5bf7a.vald.pages.dev
Branch Preview URL:	https://backport-release-v1-7-fix-ci-7l8v.vald.pages.dev

View logs

[coderabbitai]

Walkthrough

Walkthrough

A new GitHub Actions workflow has been added to automate the building of a Docker image named "buildbase." This workflow is triggered by various conditions, including pushes to specific branches and pull requests. The Makefile and Docker-related build scripts have been updated to support the naming and building of this Docker image, and a new Dockerfile has been introduced to define the image itself.

Changes

File	Change Summary
.github/workflows/dockers-buildbase-image.yml	Added GitHub Actions workflow for building the "buildbase" Docker image.
Makefile	Declared BUILDBASE_IMAGE with the value $(NAME)-buildbase.
Makefile.d/docker.mk	Added targets for building the buildbase Docker image.
dockers/buildbase/Dockerfile	Created a new Dockerfile for the buildbase image, using ubuntu:devel as the base image and including licensing information.

Sequence Diagram(s)

sequenceDiagram
    participant Developer
    participant GitHub
    participant GitHub Actions
    participant Docker Hub

    Developer->>GitHub: Push code / Create PR
    GitHub-->>GitHub Actions: Trigger workflow
    GitHub Actions->>GitHub Actions: Run `dockers-buildbase-image.yml`
    GitHub Actions->>Docker Hub: Build and push `buildbase` image
    Docker Hub-->>GitHub Actions: Confirmation of image build
    GitHub Actions-->>Developer: Notify build success/failure

Loading

---

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

[vdaas-ci]

[CHATOPS:HELP] ChatOps commands.

• 🙆‍♀️ /approve - approve
• 🍱 /format - format codes and add licenses
• ✅ /gen-test - generate test codes
• 🏷️ /label - add labels
• 🔚 2️⃣ 🔚 /label actions/e2e-deploy - run E2E deploy & integration test

[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 c6777f3 and 8251050.

Files selected for processing (4)

• .github/workflows/dockers-buildbase-image.yml (1 hunks)
• Makefile (1 hunks)
• Makefile.d/docker.mk (1 hunks)
• dockers/buildbase/Dockerfile (1 hunks)

Files skipped from review due to trivial changes (2)

• Makefile
• dockers/buildbase/Dockerfile

Additional comments not posted (3)

.github/workflows/dockers-buildbase-image.yml (2)

42-48: Confirm the job definition and parameters in the GitHub Actions workflow.

The job is correctly using a reusable workflow (._docker-image.yaml) with specific parameters set for the buildbase target and platforms (linux/amd64,linux/arm64). This is a good practice for modularity and reusability. Ensure that the secrets: inherit setting is appropriate for this context, particularly in terms of security.

---

17-41: Review the trigger conditions for the GitHub Actions workflow.

The workflow is set to trigger on a schedule, pushes to specific branches and tags, and pull requests. Ensure that these triggers align with the intended use cases for building the Docker image. The exclusion of certain release branch patterns (!release/v*.*.*) and inclusion of others (release/v*.*) should be verified for consistency with the project's versioning strategy.

Verification successful

---

Review the trigger conditions for the GitHub Actions workflow.

The workflow in .github/workflows/dockers-buildbase-image.yml is set to trigger on a schedule, pushes to specific branches and tags, and pull requests. The branch and tag patterns align with the intended use cases for building the Docker image. The exclusion of certain release branch patterns (!release/v*.*.*) and inclusion of others (release/v*.*) appear consistent with the project's versioning strategy.

• .github/workflows/dockers-buildbase-image.yml: Verified branch and tag patterns.

Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify the consistency of branch patterns in the workflow triggers.

# Test: Search for branch patterns in the repository to confirm their usage.
rg --type yaml -A 5 $'branches:'

Length of output: 31

---

Script:

#!/bin/bash
# Description: Verify the consistency of branch patterns in the workflow triggers.

# Test: Search for branch patterns in the repository to confirm their usage.
rg --type yaml -A 10 'branches:'

Length of output: 32

---

Script:

#!/bin/bash
# Description: Comprehensive search for branch patterns and trigger configurations in YAML files.

# Test: Search for branch patterns and other trigger configurations in the repository.
rg --type yaml -A 15 'branches:|tags:|paths:'

Length of output: 1671

---

Script:

#!/bin/bash
# Description: Search for branch and tag patterns specifically within the .github/workflows directory.

# Test: Search for branch and tag patterns in the .github/workflows directory.
rg --type yaml -A 15 'branches:|tags:' .github/workflows

Length of output: 51453

Makefile.d/docker.mk (1)

178-187: Review the new Makefile targets for the buildbase Docker image.

The new targets docker/name/buildbase and docker/build/buildbase are correctly defined to handle the naming and building of the buildbase Docker image. Ensure that the DOCKERFILE and IMAGE variables are appropriately set in the context of the project's Docker strategy. It's also important to confirm that these targets integrate well with existing Docker build processes.