-
Notifications
You must be signed in to change notification settings - Fork 1.1k
enhance: remove jindoruntime's fsGroup #3632
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
enhance: remove jindoruntime's fsGroup #3632
Conversation
Signed-off-by: trafalgarzzz <trafalgarz@outlook.com>
Signed-off-by: trafalgarzzz <trafalgarz@outlook.com>
Signed-off-by: trafalgarzzz <trafalgarz@outlook.com>
Signed-off-by: trafalgarzzz <trafalgarz@outlook.com>
Codecov ReportAttention:
Additional details and impacted files@@ Coverage Diff @@
## master #3632 +/- ##
=======================================
Coverage 64.26% 64.27%
=======================================
Files 443 443
Lines 26739 26749 +10
=======================================
+ Hits 17185 17193 +8
- Misses 7541 7542 +1
- Partials 2013 2014 +1 ☔ View full report in Codecov by Sentry. |
Signed-off-by: trafalgarzzz <trafalgarz@outlook.com>
|
/test fluid-e2e |
| // the dataset is set to ReadWriteMany explicitly. | ||
| ufsVolumeReadOnly := true | ||
| accessModes := dataset.Spec.AccessModes | ||
| if len(accessModes) == 1 && accessModes[0] == corev1.ReadWriteMany { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
How bout ReadWriteOnce?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ReadWriteOnce is now not supported for Fluid datasets.
| {{- else if .Values.nodeSelector }} | ||
| {{ toYaml .Values.nodeSelector | trim | indent 8 }} | ||
| {{- end }} | ||
| securityContext: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please also update chart version and changelog. thanks.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done
Signed-off-by: trafalgarzzz <trafalgarz@outlook.com>
cheyang
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
/approve
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: cheyang The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
Kudos, SonarCloud Quality Gate passed!
|
* Remove jindofsx's securityContext.fsGroup Signed-off-by: trafalgarzzz <trafalgarz@outlook.com> --------- Signed-off-by: trafalgarzzz <trafalgarz@outlook.com>
* Remove jindofsx's securityContext.fsGroup Signed-off-by: trafalgarzzz <trafalgarz@outlook.com> --------- Signed-off-by: trafalgarzzz <trafalgarz@outlook.com> Signed-off-by: cheyang <cheyang@163.com>
* enhance: remove jindoruntime's fsGroup (#3632) * Remove jindofsx's securityContext.fsGroup Signed-off-by: trafalgarzzz <trafalgarz@outlook.com> --------- Signed-off-by: trafalgarzzz <trafalgarz@outlook.com> Signed-off-by: cheyang <cheyang@163.com> * Mount ufs volumes according to datasets' accessModes, To #53506158 Signed-off-by: cheyang <cheyang@163.com> * Mount ufs volumes according to datasets' accessModes, To #53506158 Signed-off-by: cheyang <cheyang@163.com> --------- Signed-off-by: trafalgarzzz <trafalgarz@outlook.com> Signed-off-by: cheyang <cheyang@163.com> Co-authored-by: TzZtzt <trafalgarz@outlook.com>








Ⅰ. Describe what this PR does
fsGrouprelated transformation in Jindofsx and JindoCache engine.fsGrouphas no critical effect on JindoRuntime's functionality but it will chown mounted persistent volumes which may cause unexpected changes on file ownership and permissions. See Configure volume permission and ownership change policy for Pods for more information:ReadWriteManyⅡ. Does this pull request fix one issue?
fixes #XXXX
Ⅲ. List the added test cases (unit test/integration test) if any, please explain if no tests are needed.
Ⅳ. Describe how to verify it
Ⅴ. Special notes for reviews