ci: add pre-baked base image workflow#6967
Conversation
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
|
@tennix: The following tests failed, say
Full PR test history. Your PR dashboard. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
Summary
release-1.xCI base images:backup-manager-base: PingCAP QE base + backup-manager external tools (rclone,shush) and required packages.e2e-base: Debian bookworm + e2e tools (kubectl,helm, AWS CLI, cert-manager manifest) and required packages.CI Base Imagesworkflow to build both images forlinux/amd64,linux/arm64.Motivation
release-1.xCI/Prow flakes are mostly caused by downloading external binaries during normal Docker image builds. This PR adds the pre-baked image definitions and publish workflow first. After the images are published and verified pullable, a follow-up PR will update the existing Dockerfiles to consume the pre-baked images.Validation
git diff --checkbuild/ci-images/backup-manager-baselocally forlinux/arm64and verified the Dockerfile check step:env -u RCLONE_VERSION rclone versioncommand -v shushbuild/ci-images/e2e-baselocally forlinux/arm64and verified the Dockerfile check step:kubectl version --client=true --output=yamlhelm version --shortaws --versiontest -s /cert-manager.yamlFollow-up
After this workflow publishes a stable tag, open a second PR to update:
images/tidb-backup-manager/Dockerfileimages/tidb-backup-manager/Dockerfile.e2etests/images/e2e/Dockerfileto use the published pre-baked images instead of downloading external binaries during normal CI/CD builds.