Fix RustFS tenant pod permissions and add log volume #58
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
🐛 Bug Fix
This PR addresses the "Permission denied" issue reported in rustfs/rustfs#987 when bootstrapping clusters on storage backends like Longhorn or local paths where default volume permissions are
root:root.🛠 Changes
Security Context Enforcement:
PodSecurityContextto run as non-root user10001(RustFS default).fsGroup: 10001andfsGroupChangePolicy: "OnRootMismatch"to ensure Kubernetes recursively changes ownership of mounted PVCs to the RustFS user.Log Volume Management:
EmptyDirvolume mounted at/logs.🧪 Testing
test_statefulset_sets_security_context_and_log_volumeto verify that### 🐛 Bug FixThis PR addresses the "Permission denied" issue reported in #987 when bootstrapping clusters on storage backends like Longhorn or local paths where default volume permissions are
root:root.🛠 Changes
Security Context Enforcement:
PodSecurityContextto run as non-root user10001(RustFS default).fsGroup: 10001andfsGroupChangePolicy: "OnRootMismatch"to ensure Kubernetes recursively changes ownership of mounted PVCs to the RustFS user.Log Volume Management:
EmptyDirvolume mounted at/logs.🧪 Testing
test_statefulset_sets_security_context_and_log_volumeto verify that