Skip to content

CTX7-1846: Helm deployment docs page - #2925

Open
fahreddinozcan wants to merge 4 commits into
masterfrom
ctx7-1846-helm-manifests
Open

CTX7-1846: Helm deployment docs page#2925
fahreddinozcan wants to merge 4 commits into
masterfrom
ctx7-1846-helm-manifests

Conversation

@fahreddinozcan

Copy link
Copy Markdown
Collaborator

Adds the Helm deployment page for Context7 On-Premise, alongside the Helm chart PR (upstash/context7parser#574). Split out of the scaling docs PR so the chart and its docs ship together.

  • Install (single container and multi-replica), ingress, migration Job, and a values reference.
  • Adds the page to the Deployment nav group.

Note: the page links to /enterprise/deployment/scaling, which lands with the scaling docs PR (branch ctx7-1837-scaling-docs). Merge order: scaling docs first, then this. The docs.json nav array overlaps with that PR, so a trivial rebase may be needed depending on merge order.

Install, scale, ingress, migration, and values reference for the Context7
On-Premise Helm chart. Split from the scaling docs so it ships with the chart PR.
@linear-code

linear-code Bot commented Jul 20, 2026

Copy link
Copy Markdown

CTX7-1846

@mintlify

mintlify Bot commented Jul 20, 2026

Copy link
Copy Markdown

Preview deployment for your docs. Learn more about Mintlify Previews.

Project Status Preview Updated (UTC)
context7 🟢 Ready View Preview Jul 20, 2026, 8:34 AM

💡 Tip: Enable Workflows to automatically generate PRs for you.

@mintlify

mintlify Bot commented Jul 20, 2026

Copy link
Copy Markdown

Preview deployment for your docs. Learn more about Mintlify Previews.

Project Status Preview Updated (UTC)
context7 🟡 Building Jul 20, 2026, 8:33 AM

💡 Tip: Enable Workflows to automatically generate PRs for you.

@enesgules

Copy link
Copy Markdown
Collaborator

Nice page — matches the chart exactly (commands, service name, values table all check out). Three comments, only the first one matters:

  1. The migration example's dataPvcName=context7-data will trip up people who installed with this chart. For them, the volume Kubernetes actually created is named data-<release>-context7-enterprise-0 (e.g. data-context7-context7-enterprise-0), not context7-data — that name only fits people coming from the raw Kubernetes guide. Worth adding a line like: "if you installed with the chart, find your volume with kubectl get pvc — it's named data-<release>-context7-enterprise-0."

  2. Just confirming the scaling docs PR merges before this one, since this page links to /enterprise/deployment/scaling — otherwise those links 404 briefly. (Already flagged in the description.)

  3. Tiny consistency nit: this page says the migration copies SQLite and the LanceDB index, while the chart README only mentions SQLite. This version seems to be the complete one — the chart README could be aligned in a follow-up.

@fahreddinozcan

Copy link
Copy Markdown
Collaborator Author

Addressed in 410d936:

  1. Added a line to the migration step: find the PVC with kubectl get pvc -n context7; chart installs name it data-<release>-context7-enterprise-0, and context7-data matches the raw Kubernetes guide.
  2. The scaling page is already on master (this branch just merged it in while resolving the nav conflict), so the links resolve.
  3. Chart README aligned (SQLite + LanceDB index wording) in upstash/context7parser#637.

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