-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Migrate to UBI based go-build #8103
Conversation
2b6cb12
to
672aaf8
Compare
672aaf8
to
5661980
Compare
3d7a251
to
7e3f42d
Compare
7e3f42d
to
1ff49c2
Compare
033dcc3
to
df656b9
Compare
@@ -107,10 +105,6 @@ endif | |||
else ifeq ($(ARCH), $(filter $(ARCH),arm64)) | |||
CGO_ENABLED=0 | |||
REGISTRAR_BUILD_CMD=$(REGISTRAR_TIGERA_BUILD_CMD) | |||
else ifeq ($(ARCH), $(filter $(ARCH),armv7)) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@hjiawei are we going to stop publishing armv7 images?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That is correct. Kubernetes dropped 32bit arm support from v1.27+ and this is communicated/agreed with PM.
df656b9
to
9c7c060
Compare
d89ea5d
to
6b56feb
Compare
6b56feb
to
b04065a
Compare
First for amd64.
k8s dropped 32 bit linux/arm support from v1.27+ [1]. [1] kubernetes/kubernetes#115742
We use $BINARY_NAME-$ARCH format in Calico builds and packaging containers. The hard link targets in Makefile are not used and can be removed. When building multiarchs, new links without $ARCH in the binary name will overwrite existing ones which may cause unexpected behaviors.
b04065a
to
004a6e3
Compare
Description
This PR contains the following changes:
Related issues/PRs
Todos
Release Note
N/A
Reminder for the reviewer
Make sure that this PR has the correct labels and milestone set.
Every PR needs one
docs-*
label.docs-pr-required
: This change requires a change to the documentation that has not been completed yet.docs-completed
: This change has all necessary documentation completed.docs-not-required
: This change has no user-facing impact and requires no docs.Every PR needs one
release-note-*
label.release-note-required
: This PR has user-facing changes. Most PRs should have this label.release-note-not-required
: This PR has no user-facing changes.Other optional labels:
cherry-pick-candidate
: This PR should be cherry-picked to an earlier release. For bug fixes only.needs-operator-pr
: This PR is related to install and requires a corresponding change to the operator.