No write permissions on the persistent volumes using the Helm chart on some storage class. #427
Labels
No Label
AdminAPI
Bug
Check AWS
CI
Correctness
Critical
Documentation
Ideas
Improvement
Low priority
Newcomer
Performance
S3 Compatibility
Testing
Usability
No Milestone
No Assignees
3 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: Deuxfleurs/garage#427
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Hei,
I deployed garage on Kubernetes 1.25 (K3S) using the helm chart from the garage repository.
Using the K3S standard
local-path
storage class, the permissions of/mnt/meta
and/mnt/data
are both777
and owned byroot:root
. garage runs with the user1000
and it is able to write correctly.However when using the
openebs-zfspv
storage class, the permissions are755
still owned byroot:root
and garage cannot write.I fixed the configuration problem by setting the following pod security context in the
values.yaml
file:This may be necessary to put by default (I'm not sure about the
fsGroupChangePolicy
).Also, checking the permissions could be done during startup to crash early, or also checked during the readyness check as discussed in the matrix channel.
I've also stumpled onto this and added fixes in this PR: #425
Feel free to test and provide feedback on the pullrequest
@1
Since #425 was merged, this should be resolved by now
Closing for now, feel free to re-open if this issue is not solved