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

Add runtimeClassName support to helm chart #15217

Closed
dnskr opened this issue Jul 2, 2022 · 2 comments · Fixed by #15385
Closed

Add runtimeClassName support to helm chart #15217

dnskr opened this issue Jul 2, 2022 · 2 comments · Fixed by #15385

Comments

@dnskr
Copy link
Contributor

dnskr commented Jul 2, 2022

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 discussions and require runtimeClassName to be set on MinIO pods.

Describe the solution you'd like
Add runtimeClassName value to minio helm chart.

@steve-gray
Copy link

As per #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.

@harshavardhana
Copy link
Member

This is a low priority to get runtimeClassName support for vanilla helm chart - it's the operator issue minio/operator#1194 that is of high priority.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jul 23, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants