-
Notifications
You must be signed in to change notification settings - Fork 1k
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
feat: Added pvc accessModes support #4851
Conversation
15b7b61
to
8863e76
Compare
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 create a GH issue for this change
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 link the relevant GH issue
infra/feast-operator/internal/controller/featurestore_controller_pvc_test.go
Outdated
Show resolved
Hide resolved
Done. Thanks for the reminder. |
Signed-off-by: dandawg <[email protected]>
Signed-off-by: dandawg <[email protected]>
Signed-off-by: dandawg <[email protected]>
Signed-off-by: dandawg <[email protected]>
3144171
to
f02f797
Compare
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.
one nit, otherwise lgtm
What this PR does / why we need it:
This PR updates the feast services structure to allow for users to use a valid PVC accessModes list of their choosing. The default is set to ["ReadWriteOnce"], for cases where a PVC config is included in the spec, but the accessModes field is not included.
Previously, the PVC accessModes list was hard-coded to ["ReadWriteMany"] (for each of the Feast services where PVCs were used).
Which issue(s) this PR fixes:
#4853
Misc