Skip to content

docs: add Feast feature store page to MLOps - #22

Open
tmvfb wants to merge 3 commits into
stagingfrom
docs/feast-feature-store
Open

docs: add Feast feature store page to MLOps#22
tmvfb wants to merge 3 commits into
stagingfrom
docs/feast-feature-store

Conversation

@tmvfb

@tmvfb tmvfb commented Aug 6, 2026

Copy link
Copy Markdown
Member

Summary

Documents Feast, the opt-in feature store integration that's moving from
prokube#276 into
prokube-neo#29. Users
provision their own Redis online store, secret, and FeatureStore CR from
their workspace namespace — no admin action beyond enabling the operator.

Changes

  • New page mlops/feast.md (development only): stores overview, setup steps
    (Redis CR, secret, FeatureStore CR), notebook workflow, the optional
    persistent-registry Istio workaround, isolation model, troubleshooting
  • Linked from mlops/index.md's workflow table
  • mlops/feast.html added to the sidebar scoped to development only,
    since Feast has not shipped in a released version. This required adding a
    per-item versions filter to SidebarItem in config.mts — the 1.9
    sidebar/nav is unaffected, and no 1.9 page was added since one doesn't
    exist for the released version.

Rewritten for this site's structure/tone per AGENTS.md, not copied verbatim
from the legacy prokube mkdocs pages (docs/docs/user_docs/feast.md,
docs/docs/admin_docs/feast.md).

Verification command

npm run build

Confirmed docs/.vitepress/dist/development/mlops/feast.html is generated
and no 1.9/mlops/feast.html exists.

tmvfb added 3 commits August 6, 2026 14:36
Documents the Feast integration that is moving from prokube#276 into
prokube-neo (prokube-neo#29): an opt-in, self-service feature store.
Users provision their own Redis online store, secret, and FeatureStore
CR from their workspace namespace — no admin action beyond enabling
the operator.

- New page: mlops/feast.md — stores overview, setup (Redis CR, secret,
  FeatureStore CR), notebook workflow, the optional persistent-registry
  Istio workaround, isolation model, and troubleshooting
- Linked from mlops/index.md's workflow table
- Added to the sidebar under development only, since Feast has not
  shipped in a released version yet. This introduces a per-item
  `versions` filter on SidebarItem (mirrors the pattern used for
  other unreleased-only pages) so the 1.9 sidebar and nav are
  unaffected — 1.9 has no corresponding page and none was added.

Rewritten for this site's structure and tone per AGENTS.md, not copied
verbatim from the legacy prokube mkdocs pages.

@hsteude hsteude left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Added 2 minor comments, will need to test it tho. And: do we still need the example PR if we have this?

@@ -0,0 +1,192 @@
# Feast Feature Store

Feast manages reusable ML features for training and online inference. In prokube, each workspace provisions its own `FeatureStore`, Redis online store, and persistent volumes.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

on demand only?


| Store | prokube default |
|---|---|
| Registry | SQLite on an operator-created PVC |

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@Korel : Can you challenge this? I remember you talking about postgres instead of pvc

### 1. Create Redis

```bash
kubectl create secret generic redis-feast \

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

add ad comment saying that this also works comfortable from the ui (inkluding link to kubernetes secrets) :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants