Minio for pipeline no longer starts on some clusters #3040
Description
Validation Checklist
- I confirm that this is a Kubeflow-related issue.
- I am reporting this in the appropriate repository.
- I have followed the Kubeflow installation guidelines.
- The issue report is detailed and includes version numbers where applicable.
- This issue pertains to Kubeflow development.
- I am available to work on this issue.
- You can join the CNCF Slack and access our meetings at the Kubeflow Community website. Our channel on the CNCF Slack is here #kubeflow-platform.
Version
master
Detailed Description
When the mino pod starts, the logs have the following error:
┏━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┓
┃ You are running an older version of MinIO released 5 years ago ┃
┃ Update: https://docs.min.io/docs/deploy-minio-on-kubernetes ┃
┗━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┛
ERROR Unable to initialize backend: Unable to write to the backend
> Please ensure MinIO binary has write permissions for the backend
HINT:
Verify if MinIO binary is running as the same user who has write permissions for the backend
The /data directory is
drwxr-xr-x 2 root root 4096 Mar 6 23:10 data
which means given the new securityContext, there is no way to write to /data.
Easiest solution is to add
securityContext:
fsGroup: 1000
Steps to Reproduce
Launch the pipeline app.
Screenshots or Videos (Optional)
No response