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

Allow using of latest cpuv1 image for tenant #1961

Closed
zdzichu opened this issue Jan 31, 2024 · 1 comment
Closed

Allow using of latest cpuv1 image for tenant #1961

zdzichu opened this issue Jan 31, 2024 · 1 comment

Comments

@zdzichu
Copy link

zdzichu commented Jan 31, 2024

Is your feature request related to a problem? Please describe.
Some servers (like my k8s nodes) require a -cpuv1 container image; see minio/minio#18365
Operator's tenant console allows specifying the image. At the same time, the description hints If blank, then latest build will be used.
There's no way to get latest and cpuv1 at the same time. To get cpuv1 image, I need to provide exact RELEASE-x.y image.

Describe the solution you'd like
I would like to have latest and cpuv1 at the same time. I.e. I would like to be able to leave Image empty, to get the latest image, but at the same time I would like to specify that I need a cpuv1 image.
A checkbox would be enough, I think.

Describe alternatives you've considered
I don't see any alternatives.

Additional context
image

@harshavardhana
Copy link
Member

Operator is not meant to be used on legacy hardware. Unfortunately we may not be able to support it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants