docs: add llama stack vector store examples

[davidwtf]

Summary by CodeRabbit

• Documentation
  • Expanded installation guidance for Kubernetes deployments with explicit PostgreSQL configuration requirements and vector store setup details
  • Clarified vector store feature documentation to specify explicit provider IDs for PGVector and Milvus-remote configurations
  • Updated quickstart notebook with PGVector and Milvus usage examples, shared embedding model selection, and bumped client dependency version from 0.6.0 to 0.7.1

[coderabbitai]

Warning

Rate limit exceeded

@davidwtf has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 51 minutes and 40 seconds before requesting another review.

You’ve run out of usage credits. Purchase more in the billing tab.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: a456a19d-5c89-49c0-870d-eeb503e4843c

📥 Commits

Reviewing files that changed from the base of the PR and between 6d07970 and db670e1.

📒 Files selected for processing (4)

• docs/en/llama_stack/install.mdx
• docs/en/llama_stack/overview/features.mdx
• docs/en/llama_stack/quickstart.mdx
• docs/public/llama-stack/llama-stack_quickstart.ipynb

Walkthrough

This PR expands Llama Stack documentation to support client-driven vector store provider selection for both PGVector and Milvus backends. It updates installation guidance with PostgreSQL persistence requirements, clarifies the new provider_id based vector store API, and adds practical examples in the quickstart notebook.

Changes

Vector Store Expansion and Dual Backend Support

Layer / File(s)	Summary
Vector Store Provider API Conceptual Shift docs/en/llama_stack/overview/features.mdx	Features overview rewords vector store APIs to describe client-driven creation and querying with explicit provider_id values ("pgvector" and "milvus-remote") instead of server-side configuration language.
Kubernetes Installation Guide for PostgreSQL and Vector Stores docs/en/llama_stack/install.mdx	Installation docs expand with explicit POSTGRES_* environment variable requirements (including secret-backed password), extended YAML manifest example showing PostgreSQL persistence configuration, dedicated "Configure PostgreSQL Storage" section, and complete guidance for enabling PGVector and Milvus with sentence-transformers embeddings and model caching strategies.
Quickstart Guide Prerequisites and Vector Store Usage docs/en/llama_stack/quickstart.mdx	Prerequisites updated to require POSTGRES_* configuration alongside VLLM_URL endpoint. New "Vector Store Usage" section documents optional flows for both pgvector and milvus-remote providers, covering embedding model prerequisites, file upload, vector store creation with provider_id parameters, and search operations including hybrid search details.
Quickstart Notebook: Shared Embedding Model Selection and Milvus Demo docs/public/llama-stack/llama-stack_quickstart.ipynb	Notebook bumps llama-stack-client from 0.6.0 to 0.7.1, restructures Section 4 into shared "Vector Store Examples" with robust embedded model selection logic (handles multiple response shapes, resolves dimension from metadata with fallbacks), and adds new Milvus vector store example mirroring PGVector flow with file upload, provider_id="milvus-remote" creation, and search results.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

Poem

🐰 A rabbit hops through docs so bright,
Two vector stores now see the light—
From PGVector's tried and true,
To Milvus remote, shiny new.
With embeddings cached and config clear,
The stack's expansion brings us cheer! 🌟

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately summarizes the main objective of the pull request, which is to add vector store examples (both PGVector and Milvus) across installation, quickstart, and notebook documentation.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch feat/llama-stack-milvus

Tip

💬 Introducing Slack Agent: The best way for teams to turn conversations into code.

Slack Agent is built on CodeRabbit's deep understanding of your code, so your team can collaborate across the entire SDLC without losing context.

• Generate code and open pull requests
• Plan features and break down work
• Investigate incidents and troubleshoot customer tickets together
• Automate recurring tasks and respond to alerts with triggers
• Summarize progress and report instantly

Built for teams:

• Shared memory across your entire org—no repeating context
• Per-thread sandboxes to safely plan and execute work
• Governance built-in—scoped access, auditability, and budget controls

One agent for your entire SDLC. Right inside Slack.

👉 Get started

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@docs/en/llama_stack/quickstart.mdx`:
- Around line 12-15: Update the pinned client version in the quickstart docs:
replace the dependency string `llama-stack-client==0.6.0` with
`llama-stack-client==0.7.1` in the quickstart text so it matches the notebook
`llama-stack_quickstart.ipynb` and avoids version drift; ensure any surrounding
instructional text remains accurate after the change.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 0b75d6b6-7d31-4af1-beb7-dee5c59565eb

📥 Commits

Reviewing files that changed from the base of the PR and between 3cdcf6d and 6d07970.

📒 Files selected for processing (4)

• docs/en/llama_stack/install.mdx
• docs/en/llama_stack/overview/features.mdx
• docs/en/llama_stack/quickstart.mdx
• docs/public/llama-stack/llama-stack_quickstart.ipynb

[cloudflare-workers-and-pages]

Deploying alauda-ai with    Cloudflare Pages

Latest commit:	db670e1
Status:	✅  Deploy successful!
Preview URL:	https://78ffeba1.alauda-ai.pages.dev
Branch Preview URL:	https://feat-llama-stack-milvus.alauda-ai.pages.dev

View logs