-
Notifications
You must be signed in to change notification settings - Fork 459
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
Add runtimeClassName support to Tenant CRD #1194
Comments
As per minio/minio#15217 and the associated discussions, without this work to enable skipping of most of the leg-work of an SELinux relabel, it's essentially impossible to use Minio in any modern managed Kubernetes environment. As most platforms default to an SELinux variant (EKS, OCI/EKS, AKS etc....), it essentially means a restart of Minio with a scaled number of files can take exponential amounts of time, and lead to low availability of the service. |
@Alevsk @dvaldivia Hi! Are you planning to work on this issue any time soon? If not, I can try to do it. Unfortunately I'm not familiar with go and operator code base. So I would appreciate your guidance or just one or two similar PRs as the examples. |
@dnskr it's a sort of an easy issue, I can work on this before the next release |
Great! In this case I would prefer to leave it to you, since I don't feel it's easy for me. |
@dnskr the PR is up, you can review it to get an idea on how to do this changes, it's sort of straight forward |
Most of the auto-generate code can be generated with our |
Is your feature request related to a problem? Please describe.
The feature request related to the problem with files relabeling when MinIO pods run on nodes with enabled SELinux.
The solution described in the discussion and require
runtimeClassName
to be set on MinIO pods.Describe the solution you'd like
Support for
runtimeClassName
needs to be added to Tenant CRD and tenant helm chart.The text was updated successfully, but these errors were encountered: