Skip to content

fix: ensure that the controller and gateway can be deployed to the master and the tainted node #2903

fix: ensure that the controller and gateway can be deployed to the master and the tainted node

fix: ensure that the controller and gateway can be deployed to the master and the tainted node #2903

Triggered via pull request January 26, 2025 17:10
Status Success
Total duration 4m 55s
Artifacts 13

ci-patch-image.yml

on: pull_request
call_ci_workflow  /  test
0s
call_ci_workflow / test
save-sealos  /  save-sealos
20s
save-sealos / save-sealos
call_ci_workflow  /  resolve-modules
7s
call_ci_workflow / resolve-modules
call_ci_workflow  /  resolve-modules-arch
6s
call_ci_workflow / resolve-modules-arch
Matrix: call_ci_workflow / build
Matrix: call_ci_workflow / docker
container-sealos
0s
container-sealos
build-on-cluster-patch-image
0s
build-on-cluster-patch-image
build-on-cluster-image
0s
build-on-cluster-image
Fit to window
Zoom out
Zoom in

Annotations

6 warnings
call_ci_workflow / docker (arm64)
Unable to delete artifact "lvscare-arm64"; the artifact was not found.
call_ci_workflow / docker (arm64)
Unable to delete artifact "sealctl-arm64"; the artifact was not found.
call_ci_workflow / docker (arm64)
Unable to delete artifact "image-cri-shim-arm64"; the artifact was not found.
call_ci_workflow / docker (amd64)
Unable to delete artifact "lvscare-amd64"; the artifact was not found.
call_ci_workflow / docker (amd64)
Unable to delete artifact "sealctl-amd64"; the artifact was not found.
call_ci_workflow / docker (amd64)
Unable to delete artifact "image-cri-shim-amd64"; the artifact was not found.

Artifacts

Produced during runtime
Name Size
image-cri-shim-amd64
6.23 MB
image-cri-shim-arm64
5.64 MB
labring~sealos~IOR0HD.dockerbuild
23.5 KB
labring~sealos~ZHQ8AY.dockerbuild
23.3 KB
lvscare-amd64
10.4 MB
lvscare-arm64
9.29 MB
patch-image-amd64.tar
50.3 MB
patch-image-arm64.tar
45.6 MB
sealctl-amd64
28.5 MB
sealctl-arm64
25.4 MB
sealos
25.7 MB
sealos-amd64
30 MB
sealos-arm64
26.7 MB