fix: Add missing feast init templates to operator CRD and enhance persistence documentation#6402
Merged
Merged
Conversation
franciscojavierarceo
approved these changes
May 28, 2026
…sistence documentation Signed-off-by: ntkathole <nikhilkathole2683@gmail.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
What this PR does / why we need it:
02-persistence.md) with comprehensive Secret/ConfigMapdocumentation for all operator-supported store types. Users were struggling to create the correct Secret or ConfigMap for different online/offline/registry store backends. The existing
02-persistence.mdcovered thepattern at a high level but lacked copy-paste-ready examples for most store types.
feast inittemplate types (milvus,ray,ray_rag,pytorch_nlp) to theFeastInitOptions.Templateenum in the operator CRD, aligning it with the SDK CLI'ssupported templates.