normalize the image building targets #8400
Open
+91
−113
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What type of PR is this?
/kind cleanup
What this PR does / why we need it:
This PR fixes the post-provider-azure-push-images job failure which is caused by building windows images and out to Linux docker Engine. Fix this by normalizing the image building targets.
docker buildx --output=type=registry
which can reuse the build target but specify OUTPUT_TYPE=registry. pushing images does not relies on building image targets in the future.Besides fixing the image building job issue. we also
$NODE_MANAGER_FULL_IMAGE_NAME
and$ALL_NODE_MANAGER_IMAGES
, and use$(NODE_MANAGER_IMAGE):$(IMAGE_TAG)
specificly to represent the image+tag, and useforeach
to iterate the OS and ARCH to form the image tags for different OS and ARCH.make help
WINDOWS_USE_HOST_PROCESS_CONTAINERS
is set to trueFinally, in order to not break the PR check-in and post-provider-azure-push-images, we introduced
IS_RELEASE
variable. PR check-in in capz ci-build-azure-ccm.sh build and publish amd64 ccm images, but expect a arch-agnostic image inappropriately, we keep this ability and hope to replace it withmake ALL_ARCH.linux=amd64 manifest-controller-manager
after this PR is merged.Tests have been done:
I have tested this change against ado pipeline, pr check-in, and post-provider-azure-push-images job.
ordinary image push
node manager manifest with windows host process contianer image
current capz support
future capz change
capz can still build only minimal amd64-based image for test as it has been doing so far.
release
for ado pipelines,
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.: