Add the Service to automatically build a cluster-image.

[bxy4543]

🤖 Generated by Copilot at 11fe3ac

Summary

🐳🚀📊

This pull request updates the cloud deployment and the database service to use sealos cluster images. It adds a GitHub workflow job to build and sync the cluster images, modifies the init.sh script to pull and save the cluster image for the database service, and creates a Kubefile to define how to build the cluster image. It also renames and deletes some manifest files to simplify the deployment process.

To build the database cluster image
We use sealos and a Kubefile
Then we sync and deploy
With sealos and init.sh
And monitor the service with the same image

Walkthrough

• Enable and modify the build-cluster-image job in the .github/workflows/services.yml file, which uses sealos to build and push cluster images for each module (link, link)
• Add a new file called Kubefile to the service/database/deploy directory, which defines how to build the cluster image for the database service using sealos (link)
• Change the image name for the database monitor container in the service/database/deploy/manifests/deploy.yaml file, to match the new cluster image name (link)
• Rename and move the manifest files for the VictoriaMetrics components from the service/database/deploy/manifests directory to the service/database/deploy directory, to simplify the cluster image building process (link, link, link, link, link, link)
• Delete the deploy/cloud/manifests/db-metrics.yaml file, as it is no longer needed (link)
• Add commands to the init.sh script for the cloud deployment, which pull, save, and run the cluster image for the database service using sealos, to ensure the latest image is available and deployed on the cluster (link, link, link)
• Remove a command from the init.sh script for the cloud deployment, which applied a manifest file for the database metrics, as it is integrated into the cluster image (link)

[sealos-ci-robot]

🤖 Generated by lychee action

Summary

Status	Count
🔍 Total	956
✅ Successful	375
⏳ Timeouts	0
🔀 Redirected	0
👻 Excluded	580
❓ Unknown	0
🚫 Errors	0

Full action output

Full Github Actions output

[sweep-ai]

Apply Sweep Rules to your PR?

• Apply: Leftover TODOs in the code should be handled.
• Apply: All new business logic should have corresponding unit tests in the tests/ directory.
• Apply: Any clearly inefficient or repeated code should be optimized or refactored.

[codecov]

Codecov Report

All modified lines are covered by tests ✅

📢 Thoughts on this report? Let us know!.