EvalHub
EvalHub is a model evaluation service managed by the TrustyAI Operator. It provides a unified API for running AI model evaluations on Kubernetes, supporting a range of built-in evaluation providers and curated benchmark collections.
This page covers the Kubernetes and operator aspects of EvalHub: how to deploy it, how it is structured, and what built-in providers and collections are available. For SDK usage, job authoring, and the EvalHub API reference, see the EvalHub documentation.
Architecture
When an EvalHub custom resource is created, the operator deploys and manages the following Kubernetes resources:
-
EvalHub Deployment — the EvalHub API server, fronted by a
kube-rbac-proxysidecar that handles authentication and authorisation. The API is exposed over HTTPS on port 8443. -
Metrics Service — a Prometheus scraping endpoint on port 8081, with an optional
ServiceMonitorfor automatic discovery. -
Provider and Collection ConfigMaps — built-in provider and collection configuration is mounted from ConfigMaps in the operator namespace.
-
Tenant RBAC — in multi-tenancy mode, the operator propagates
RoleandRoleBindingresources into each namespace labelled as a tenant. -
MCP Server (optional) — a Model Context Protocol server deployment, also fronted by
kube-rbac-proxy, for AI agent integration.
Providers
Providers define the evaluation frameworks that EvalHub can run jobs against.
The following built-in providers are available. The default set deployed when spec.providers is not specified is garak, garak-kfp, and lm-evaluation-harness.
| Name | Description |
|---|---|
|
Accuracy and reasoning benchmarks (MMLU, HellaSwag, ARC, GSM8K, and more) via the EleutherAI LM Evaluation Harness. |
|
LLM vulnerability scanner and red-teaming framework. Supports OWASP LLM Top 10, AVID taxonomy, CWE, and toxicity probes. |
|
Garak evaluations orchestrated via a KubeFlow Pipelines backend. |
|
Performance benchmarking for LLM inference servers. Measures latency, throughput, and scaling under various load profiles. |
|
LLM quality evaluation covering hallucination, relevance, faithfulness, and G-Eval metrics. |
|
RAG pipeline evaluation: context precision, recall, faithfulness, and answer relevance. |
|
UK AISI Inspect AI framework for alignment auditing, safety benchmarks, and agentic evaluations. |
|
Lightweight LLM evaluation with a broad benchmark catalogue. |
|
IBM CLEAR error analysis and reporting framework for agentic evaluations. |
Additional tenant-scoped providers can be added by creating ConfigMaps in the EvalHub instance namespace
labelled with trustyai.opendatahub.io/evalhub-provider-type: tenant.
See Custom providers and collections for details.
Collections
Collections are curated sets of benchmarks that group related evaluation tasks under a named profile. The following built-in collections are available:
| Name | Description |
|---|---|
|
Comprehensive evaluation suite for general-purpose language models. |
|
Evaluates model safety, bias, and fairness across diverse scenarios. |
|
End-to-end safety assessment covering toxic content generation, ethical principles, and model alignment. |
|
Evaluates code generation capability of instruction-tuned chat LLMs on real-world programming tasks. |
|
Evaluates how well instruction-tuned chat LLMs follow explicit instructions across diverse task types. |
|
Evaluates long-context retrieval and comprehension for instruction-tuned chat LLMs. |
|
Evaluates multi-step and chain-of-thought reasoning for instruction-tuned chat LLMs. |
|
Evaluates model safety using context-aware vulnerability scanning. |
|
Standard evaluation protocol covering instruction following, reasoning, coding, and safety. |
Tenancy model
EvalHub supports two tenancy modes, controlled by spec.tenancy.
Multi-tenancy (multi, the default) deploys a single EvalHub instance in a control-plane namespace
that serves multiple tenant namespaces.
The operator discovers tenant namespaces by the label evalhub.trustyai.opendatahub.io/tenant=true
and propagates the necessary RBAC resources into each one.
A discovery ConfigMap (evalhub-discovery) is also created in each tenant namespace
so that clients can resolve the EvalHub service URL without hardcoding it.
Note that a multi-tenant EvalHub cannot be placed in a namespace that is itself labelled as a tenant.
Single-tenancy (single) deploys EvalHub directly in the workload namespace.
No cross-namespace label discovery or RBAC propagation is performed.
Use this mode when a dedicated EvalHub per team or environment is preferred.
In multi-tenancy mode the operator watches for namespace label changes cluster-wide and reconciles RBAC immediately when a namespace is labelled or unlabelled.