Files
cp1-agents/outcome-pattern/solution_architecture/cp1-solution-architecture-agent/kubernetes/configmap.yaml
Jonathan Boniface bc84ee4df6
Some checks failed
check agents / check (push) Failing after 13s
Solution architecture outcome pattern: agent and its MCP servers
The cp1-solution-architecture-agent and the sa-aws/azure/gcp-cloud MCP servers, a separate
stream from the individual and sub-agent patterns.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-05 22:13:25 +00:00

145 lines
8.2 KiB
YAML

apiVersion: v1
kind: ConfigMap
metadata:
name: <placeholder_for_agent_name>-config # Do not modify, this will be replaced during deployment by the CI/CD pipeline
data:
# This file is the agent's configuration contract. deployment.yaml mounts it
# with `envFrom: configMapRef`, so every key below arrives in the container as
# an environment variable. ./run-local.sh reads the same file, so local runs
# and deployed runs share one source of truth.
#
# Values are read once at process start. Changing a key requires a restart
# (`kubectl rollout restart deploy/<agent>`), not just a ConfigMap apply.
#
# Secrets do NOT belong here — see kubernetes/secretnames.yaml.
# =============================================================================
# Platform Variables (set by Kustomize/Deployment)
# =============================================================================
PORT: "8080"
LOG_LEVEL: "INFO" # DEBUG adds prompts, payloads and replies to the log
# json: one object per line, for a log store. console: aligned columns, for
# reading by eye (set it in .env on your machine).
LOG_FORMAT: "json"
# =============================================================================
# Required Agent Configuration
# =============================================================================
# The agent's name, description, version and framework -- and its tags,
# capabilities and skills -- live in agent.yaml, the source of truth for all
# of them. They are not read from here.
# LLM model (required) - MUST use *LLM_MODEL or *SLM_MODEL pattern for watcher
# Any model the platform's gateway offers, e.g. gpt-5.4, claude-sonnet-4-6.
LITELLM_MODEL: "claude-sonnet-5-5"
# Each sub-agent's model: <NAME>_LLM_MODEL for the sub-agent named <name>.
# =============================================================================
# Optional Model Settings
# =============================================================================
# These MUST carry the LITELLM_ prefix. The runtime configures the model via
# build_model(), which reads LITELLM_TEMPERATURE / LITELLM_MAX_TOKENS
# (defaults 0.0 / 16384). The unprefixed LLM_TEMPERATURE / LLM_MAX_TOKENS names
# are read by a different SDK code path that does not configure this agent's
# model, so setting those is silently ignored — the agent keeps running at the
# defaults with no error to chase.
LITELLM_TEMPERATURE: "1"
LITELLM_MAX_TOKENS: "32000"
# =============================================================================
# Agent Loop Guard Rails
# =============================================================================
# An agent with tools makes as many model calls as the model decides it
# needs. These bound that. Any one of them ends the loop, and the caller
# receives an answer explaining why rather than an error.
#
# The defaults sit well above normal work, so they catch runaways — most
# often a tool bug that keeps telling the model to call it again — without
# affecting an agent that is behaving. Measure your agent's typical call
# count in the `agent_loop_completed` log line before tightening them.
#
# An agent with no tools cannot loop: one request is one model call, and
# these settings have nothing to bound.
#
AGENT_GUARDRAILS_ENABLED: "true" # "false" removes the bounds; the run is still counted and logged
# The orchestrator makes one model call per round of MCP calls, so a scan
# batch or the analyse phase needs more than 25. Sub-agents are asked from
# code (delegate), outside the request's model-call budget, and keep their
# own per-run bound. Measure `agent_loop_completed` and set it just above.
AGENT_MAX_ITERATIONS: "60" # model calls per run: the agent's, or one sub-agent's
# Model calls in the whole request, the sub-agents the model calls included
# (runtime 0.28.2 or later). Default 4 x AGENT_MAX_ITERATIONS.
# AGENT_MAX_REQUEST_MODEL_CALLS: "100"
AGENT_MAX_DURATION_SECONDS: "1740" # wall clock per request (29 minutes): inside the workflow step's 30, so the agent replies before the step is cut off
AGENT_MAX_TOKENS: "0" # total tokens per request; 0 = no limit
# =============================================================================
# Connections: set by the platform, not here
# =============================================================================
# The model gateway (LITELLM_PROXY_BASE, GATEWAY_TYPE), the MCP gateway
# (MCP_GATEWAY_URL) and where telemetry goes (OBSERVABILITY_TYPE,
# OTEL_EXPORTER_OTLP_ENDPOINT) are the same for every agent in an environment.
# The platform supplies them in the agents namespace (ConfigMap
# agent-platform-connections), and the Deployment reads them last, so a value
# here would be overridden. Telemetry goes to the platform's OpenTelemetry
# Collector, which holds any keys. Locally, .env holds them (.env.example).
# =============================================================================
# Inbound checks (runtime 0.25.0 or later)
# =============================================================================
# What the agent accepts before any of its work starts.
AGENT_MAX_CONCURRENT_REQUESTS: "100" # one more at once gets HTTP 503, which Temporal retries
# AGENT_MAX_REQUEST_BYTES: "67108864" # 64 MiB; a larger request body gets HTTP 413
# The name of a guardrail configured on the LLM gateway. Each request's text
# is screened by it before the agent runs; a blocked request fails with the
# gateway's reason, with no model call and no cost.
# AGENT_INPUT_GUARDRAIL: ""
# AGENT_INBOUND_TOKEN is a secret, so it is not set here (see
# kubernetes/secretnames.yaml). The platform does not send it yet: leave it unset.
# =============================================================================
# Outbound connections (runtime 0.25.0 or later)
# =============================================================================
# The agent may connect to its own endpoints: the LLM gateway, the MCP
# gateway, its telemetry, localhost, and the hosts in AGENT_EGRESS_ALLOW.
# enforce (default): a connection to any other host is refused and logged
# as egress_blocked, with the file and line that made it.
# log: such a connection goes through and is logged as egress_unlisted.
# off: not watched.
# Reach outside systems through the MCP gateway rather than adding hosts here.
# The cluster's network policy remains the real boundary.
AGENT_EGRESS: "enforce"
# AGENT_EGRESS_ALLOW: "" # comma-separated hosts; *.<domain> for a domain and its subdomains
# =============================================================================
# Run workspace
# =============================================================================
# Where app/workspace.py keeps each run's records: the shared execution-storage-pvc that deployment.yaml mounts
# at /data/executions. The platform does not set this for agents in kab-dev, and without it the workspace falls
# back to /tmp/executions inside the container, which a restart wipes, and which later phases on another pod
# cannot read.
EXECUTION_STORAGE_ROOT: "/data/executions"
# =============================================================================
# Solution Architecture
# =============================================================================
TERRAFORM_BINARY: "/agent/terraform/bin/terraform"
TF_CLI_CONFIG_FILE: "/agent/terraform/terraformrc"
# Free-text documentation search sends model-written queries to the vendor,
# unscrubbed. Off until a deployment has checked the customer's contract.
CLOUD_DOCS_SEARCH: "false"
# Published modules need registry.terraform.io, which there's no offline mirror for.
TERRAFORM_MODULES: "false"
MAX_PARALLEL_SPECIALISTS: "4"
MAX_REVISIONS: "3"
SPECIALIST_BUDGET: "15"
# =============================================================================
# Observability content
# =============================================================================
# This agent handles client data. "false" keeps prompts, replies and
# tool data out of traces; the run workspace and its manifest remain the record.
OBSERVABILITY_CAPTURE_CONTENT: "false"