Resource reference
10 custom resources across 4 API groups, reconciled by 2 control planes — eks-agent-platform and eks-fleet.
Everything below is generated from the definitions those repos ship — the same files a cluster installs. A field on this page is a field the API server will accept, and a field the API server accepts is on this page.
agents.nanohype.dev
Runtime. How model access is exposed, and the shapes agent work actually runs in.
| Kind | Scope | What it is |
|---|---|---|
AgentFleet | Namespaced | AgentFleet is a Platform-scoped declaration of one or more agents, each reconciled into a Deployment running under the tenant's identity. |
AgentSandbox | Namespaced | AgentSandbox is a Platform-scoped, single-use isolated pod for one agent role-session. |
ModelGateway | Namespaced | ModelGateway is a per-Platform gateway CR that fronts Bedrock for one or more named routes. |
SandboxPool | Namespaced | SandboxPool is a Platform-scoped pool of Managed Agents self-hosted sandbox workers. |
fleet.nanohype.dev
Clusters. The order a team places to have one vended, and what the vend reports back.
| Kind | Scope | What it is |
|---|---|---|
Cluster | Namespaced | Cluster is an order for one EKS cluster. |
governance.nanohype.dev
Control loops. Spend, service level, and evaluation — each one a policy that acts, not a dashboard that reports.
| Kind | Scope | What it is |
|---|---|---|
BudgetPolicy | Namespaced | BudgetPolicy caps monthly spend per Platform and triggers the kill-switch at 120% of the threshold. |
EvalSuite | Namespaced | EvalSuite is a scheduled evaluation run against an AgentFleet's agents. |
SLOPolicy | Namespaced | SLOPolicy declares a Platform's service-level objective and turns a page-tier error-budget burn into a platform action: an event on the kill-switch bus and a hold on the tenant's rollout. |
platform.nanohype.dev
Tenancy. Who owns what, and the boundary the rest of the platform reconciles inside.
| Kind | Scope | What it is |
|---|---|---|
Platform | Namespaced | Platform is the top-level tenancy CR. Namespaced so that BudgetPolicy, ModelGateway, AgentFleet, and EvalSuite references resolve in the same namespace by name. The operator provisions the tenant workload namespace (tenants-<platform-name>) separately at reconcile time; the Platform CR itself lives in whichever namespace the cluster admin places it (typically a management namespace such as eks-agent-platform). |
Tenant | Cluster | Tenant is the cluster-scoped organizational owner of one or more Platforms. |
Reading them from a cluster
The CRDs are the contract, and a live cluster is the other copy of it. Both answer the same question, which is the point:
kubectl api-resources --api-group=agents.nanohype.dev
kubectl explain agentfleet.spec.agents
kubectl get platforms -A