Skip to Content
ReferenceResourcesResources

Resources

Ark extends Kubernetes with custom resources (CRDs) in the ark.mckinsey.com API group. Each resource is reconciled by the Ark controller, so you create and manage them with standard tools — kubectl, GitOps, the Ark API, or the dashboard. This section is the field-by-field reference for every CRD; for task-oriented guides see the User Guide.

Resource reference

ResourceKindAPI versionDescription
AgentsAgentv1alpha1Execution units that process input with a model and tools.
ModelsModelv1alpha1LLM provider configuration and credentials.
QueriesQueryv1alpha1A request to run work against an agent, team, model, or tool.
TeamsTeamv1alpha1Multi-agent coordination via an execution strategy.
ToolsToolv1alpha1Capabilities agents can call (HTTP, MCP, agent, team, built-in).
MCPServersMCPServerv1alpha1Model Context Protocol servers that expose tools.
MemoriesMemoryv1alpha1Backing store for conversation history.
A2AServersA2AServerv1prealpha1Remote Agent-to-Agent servers; discovered agents become Agent resources.
A2ATaskA2ATaskv1alpha1Tracks an async task dispatched to an A2A agent.
ExecutionEngineExecutionEnginev1prealpha1Pluggable external runtime that executes agents via the A2A protocol.
ArkConfigArkConfigv1alpha1Cluster-scoped configuration singleton (e.g. default query TTL).

Every resource is namespaced except ArkConfig, which is cluster-scoped. A2AServer and ExecutionEngine are served under ark.mckinsey.com/v1prealpha1; the rest under v1alpha1.

Working with resources

All Ark CRDs behave like native Kubernetes objects:

kubectl get agents # list, with resource-specific print columns kubectl describe agent my-agent # spec, status, and events kubectl get query my-query -o yaml # full spec + status kubectl apply -f agent.yaml # create or update

Each resource page documents its spec fields, status fields, and the print columns kubectl get renders.

Resource relationships

Ark resources compose into common patterns:

  • Agent + Model + Tools — an agent with a model and capabilities.
  • Team + Agents — multi-agent collaboration under a strategy.
  • Query + target — a request routed to an agent, team, model, or tool.
  • MCPServer + Tools — standardized tool integration; discovered tools become Tool resources.
  • Memory + Query — conversation history threaded by conversationId.
  • A2AServer + Agent — remote agents surfaced as local Agent resources.

See Resource Relationships for the full dependency map.

Last updated on