-
Notifications
You must be signed in to change notification settings - Fork 122
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
fix: gocli startup in s390x architecture #1354
base: main
Are you sure you want to change the base?
fix: gocli startup in s390x architecture #1354
Conversation
The gocli container image is multi-architecture compatible; however, it attempts to download the k8s-1.30 image, which is not available for the s390x architecture. The k8s-1.30-slim image, on the other hand, is compatible. To enable support for s390x, we can enforce the use of the --slim parameter for this architecture. Signed-off-by: Nestor Acuna Blanco <[email protected]>
[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.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/cc @chandramerla |
/test check-provision-k8s-1.31 |
1 similar comment
/test check-provision-k8s-1.31 |
@nestoracunablanco: The following tests failed, say
Instructions 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. |
The gocli container image is multi-architecture compatible; however, it attempts to download the k8s-1.30 image, which is not available for the s390x architecture. The k8s-1.30-slim image, on the other hand, is compatible. To enable support for s390x, we can enforce the use of the --slim parameter for this architecture.
Release note: