Skip to content

refactor: reorganize tenancy documentation and update architecture sections#90

Merged
ruivieira merged 2 commits into
eval-hub:mainfrom
ruivieira:feat/single-tenancy
Jul 6, 2026
Merged

refactor: reorganize tenancy documentation and update architecture sections#90
ruivieira merged 2 commits into
eval-hub:mainfrom
ruivieira:feat/single-tenancy

Conversation

@ruivieira

@ruivieira ruivieira commented Jul 6, 2026

Copy link
Copy Markdown
Member

What and why

Documents EvalHub's spec.tenancy deployment modes (multi default, single) by splitting the former single multi-tenancy page into three focused guides:

  • Tenancy overview (/architecture/tenancy/) — mode comparison, shared isolation/auth concepts, ClusterRoles reference, common troubleshooting, and mode switching
  • Multi-Tenancy (/architecture/multi-tenancy/) — trimmed setup guide for shared control-plane deployments (tenant labels, principals, per-tenant RBAC)
  • Single-Tenancy (/architecture/single-tenancy/) — new setup guide for spec.tenancy: single (convenience Roles, evalhub-user bindings, tenant ConfigMaps)

The sidebar is updated to a Tenancy group (Overview / Multi-Tenancy / Single-Tenancy), and the home page feature bullet now links to the overview.

Type

  • feat
  • fix
  • docs
  • refactor / chore
  • test / ci

Testing

  • Tests added or updated
  • Tested manually

npm run build — all three pages render successfully (mermaid diagrams, Tabs, Steps).

Breaking changes

None. Existing /architecture/multi-tenancy/ URLs are preserved; new pages are additive.

Summary by CodeRabbit

  • New Features

    • Added a new tenancy architecture guide covering both multi-tenant and single-tenant deployment modes.
    • Added a dedicated single-tenancy setup guide with deployment, access, API, and troubleshooting instructions.
  • Documentation

    • Updated the multi-tenancy guide to be shorter and link to shared tenancy concepts.
    • Improved the homepage tenancy feature link to point to the new overview documentation.

…ctions

- Updated the architecture section to group multi-tenancy and single-tenancy under a new "Tenancy" overview.
- Introduced a new "Single-Tenancy" guide detailing deployment in a single namespace.
- Enhanced the "Multi-Tenancy" guide with clearer descriptions and removed outdated content.
- Adjusted references in the home documentation to reflect the new tenancy structure.
@coderabbitai

coderabbitai Bot commented Jul 6, 2026

Copy link
Copy Markdown

Caution

Review failed

An error occurred during the review process. Please try again later.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

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

Comment @coderabbitai help to get the list of available commands.

@ruivieira ruivieira moved this from Todo to In Progress in EvalHub Planning Jul 6, 2026

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

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 `@src/content/docs/architecture/single-tenancy.mdx`:
- Line 66: The `evalhub-tenant-admin` role description is incomplete because it
only states MLflow read access and omits the `create` verb needed for evaluation
submission. Update the `single-tenancy.mdx` docs near the `evalhub-tenant-admin`
role entry to either include MLflow `create` alongside the existing permissions
or explicitly note that the role is read-only, so the documented namespace
ServiceAccount flow matches the `POST /api/v1/evaluations/jobs` requirements.
🪄 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: defaults

Review profile: CHILL

Plan: Pro

Run ID: b25dfd1f-3646-4b3f-84f1-bc518958b2dd

📥 Commits

Reviewing files that changed from the base of the PR and between fc4713a and 8961b6f.

📒 Files selected for processing (5)
  • astro.config.mjs
  • src/content/docs/architecture/multi-tenancy.mdx
  • src/content/docs/architecture/single-tenancy.mdx
  • src/content/docs/architecture/tenancy.mdx
  • src/content/docs/home.mdx

Comment thread src/content/docs/architecture/single-tenancy.mdx Outdated
- Updated the `evalhub-tenant-admin` role description to specify MLflow read-only access.
- Enhanced the default admin access note to clarify job submission requirements and permissions for `evalhub-user`.
- Added details on MLflow submission permissions related to `evaluations` and `experiments`.

@ppadashe-psp ppadashe-psp left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

lgtm

@ruivieira ruivieira merged commit d7f0726 into eval-hub:main Jul 6, 2026
2 checks passed
@github-project-automation github-project-automation Bot moved this from In Progress to Done in EvalHub Planning Jul 6, 2026
@ruivieira ruivieira deleted the feat/single-tenancy branch July 6, 2026 13:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

2 participants