Skip to content
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

kustomize v5.2.1 linux s390x #821

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

aliakseimakarau
Copy link

@aliakseimakarau aliakseimakarau commented Nov 7, 2023

Type of change

  • Refactor
  • New feature
  • Bug fix
  • Optimization
  • Documentation Update

Description

Dear Bulldozer Team!

Running the operator in the Openshift at IBM Z (s390x arch) the kustomize binary not found.
Here proposed to use a more recent version of the binary.

This is the recent version which has the s390x as well as the other archs:
https://github.com/kubernetes-sigs/kustomize/releases/tag/kustomize%2Fv5.2.1

This is the current kustomize version where only the intel arch binary is present:
https://github.com/kubernetes-sigs/kustomize/releases/tag/kustomize%2Fv3.5.4

Have a nice day!

Related Tickets & Documents

  • Related Issue #
  • Closes #

Checklist before requesting a review

  • I have performed a self-review of my code.
  • If it is a core feature, I have added thorough tests.

Testing

  • Please describe the System Under Test.
  • Please provide detailed steps to perform tests related to this code change.
  • How were the fix/results from this change verified? Please provide relevant screenshots or results.

@aliakseimakarau aliakseimakarau force-pushed the master branch 6 times, most recently from b684761 to 0c6415d Compare November 9, 2023 10:10
@krishvoor
Copy link
Member

With #822 we are in effect to publicly archive benchmark-operator.
Would encourage you looking at kube-burner-ocp which has multi-arch coverage

Copy link

stale bot commented Mar 17, 2024

Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward?

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

@stale stale bot added the not_ready label Mar 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants