-
Notifications
You must be signed in to change notification settings - Fork 29
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: correct fsGroup configuration in various deployments #974
Conversation
✅ Deploy Preview for leapfrogai-docs canceled.
|
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.
Awesome! I also [will have] fixed this here. This works locally, I but am not sure if this actually helps in a CSP deployment as well (as in, I am literally not sure and haven't tried it myself yet).
Have you tested this in an EC2-based cluster using EFS yet?
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.
Post-standup context approve!
Yes! We replicated and validated this fix on an RKE2 cluster (running on an EC2 instance) that was using |
These changes all make sense and I didn't see any issues when redeploying. |
Several (if not all 😬) of our deployments had the
fsGroup
configuration in the wrong place so it wasn't actually applying. This led to an issue where our data-injections were not working when the underlying store was not a PVC provisioned withlocal-path
as the StorageClass.This PR fixes the fsGroup key so that it is in the correct place.