-
Notifications
You must be signed in to change notification settings - Fork 928
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
fix(pipeline): minio filesystem permission access error #3045
fix(pipeline): minio filesystem permission access error #3045
Conversation
Signed-off-by: M!l!nd <[email protected]>
Tried with this fgGroup: 1000 change on minikube, but getting the following error:
|
Looks like it needs to be one level above |
Please check https://github.com/minio/minio/blob/11507d46da0c98af6066e76a58eab4e81bfb6d58/helm/minio/values.yaml#L276 So
|
Signed-off-by: Julius von Kohout <[email protected]>
/ok-to-test |
Signed-off-by: Julius von Kohout <[email protected]>
We also must open a PR against kubeflow/pipelines |
@ericgtkb @fraenkel please test this branch on your clusters and report back on which exact clusters it worked. CC @tarekabouzeid for testing as well. AKS, EKS, GKE, RANCHER would be good. |
Just confirming that it works on minikube - minio pod starts without issues. |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: juliusvonkohout The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
kubeflow/pipelines#11734 is the upstream PR. |
Pull Request Template for Kubeflow Manifests
✏️ Summary of Changes
This change will will make Kubernetes automatically set the correct ownership of the mounted volumes to be accessible by
user 1000
📦 Dependencies
🐛 Related Issues
fixes #3040
✅ Contributor Checklist