Add CP1 Discovery agents in both patterns
All checks were successful
check agents / check (push) Successful in 10s

ALZ-F01 Discovery as a sub-agent orchestrator (sub-agents/) and as eight
individual declarative agents (individual-agents/), with their KAB workflow
exports. Shared check, render and import scripts, the alz-discovery-sample
MCP server, the crucible-kab-dev deploy profile, deployment docs, platform
issue reports and the source material. Agent steps time out at 20 minutes.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
2026-10-29 18:25:57 +00:00
commit 416c66ced4
331 changed files with 33561 additions and 0 deletions

View File

@@ -0,0 +1,15 @@
# KAB's default tenant id, for mcp-gateway-link-default-tenant.job.yaml.
#
# It is an identifier, not a credential: it appears in every KAB request and in the gateway's logs. It is kept in
# a Secret only so the Job reads it the same way it reads the internal service token. stringData takes the plain
# value; Kubernetes stores it base64-encoded under data. The gateway Deployment does not read it.
apiVersion: v1
kind: Secret
metadata:
labels:
app.kubernetes.io/part-of: kab
name: kab-tenant-id
namespace: core-components
type: Opaque
stringData:
tenant-id: "6ada663eb5b88053a9e43723"