-
Notifications
You must be signed in to change notification settings - Fork 51
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
Redis pod failing to write on mounted volume resulting in pulp-content returning 500 #1354
Comments
Appearantly, fsGroup should be enabled according to redis controller code here
When checking actual Pod config:
So fsGroup defined here
|
Need to look into why User 999 is not allowed to write in the volume for the Redis image. |
Who needs to look into this? |
This was a reminder to us devs when we were triaging the issue. |
The same issue is affecting database pods created by the pulp operator. |
Version
image: quay.io/pulp/pulp-operator:v1.0.0-beta.5
default pulp images.
Describe the bug
After enabling cache, pulp-content fails with 500.
The cache pod is failing due to unsufficient privileges when writing to volume.
To enable Redis user 999 with group 999 to save on mounted storage, pod must have securityContext.fsGroup with value 999.
When I'm trying to enable this by editing Pulp CR:
To Reproduce
set Pulp CR:
kubectl apply -f pulp.yaml
strict decoding error: unknown field "spec.cache.securityContext"
Expected behavior
proper securityContext is applied and Redis is able to save RDB file.
Additional context
OVH Managed Kubernetes 1.30.2
The text was updated successfully, but these errors were encountered: