Platform scripts, MCP servers, deployment and docs for the KAB runs
- Scripts to run workflows from a YAML context or run inputs (kab_run_workflow.py, with --input name=@file), store per-project discovery connections, bootstrap agent MCP keys, refresh the KAB token, publish reports and build estate snapshots. - Hyperscaler discovery servers extended in place; cloud-knowledge folded into them. - deploy/crucible-kab-dev.yaml: the Discovery package agent and the Assessment agents. - Platform issue write-ups and current-wiring notes under docs/platform-issues/. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
@@ -4,6 +4,7 @@
|
||||
|---|---|
|
||||
| Date | 2026-10-30 |
|
||||
| Status | Built to simulated-cloud tests. See [Build status](#build-status-2026-10-30) |
|
||||
| Update 2026-11-04 | `cloud-knowledge` is retired. Guidance is a tool on `azure-discovery` and `gcp-discovery`, on the customer's connection (D9). Sections below that describe `cloud-knowledge` are history |
|
||||
| Scope | Three read-only MCP servers that collect metadata from a customer's cloud estate for CP1 Discovery (ALZ-F01), one folder each under `mcp-servers/` |
|
||||
| Reference for Azure | [Azure MCP Server](https://github.com/microsoft/mcp/blob/main/servers/Azure.Mcp.Server/README.md) |
|
||||
| Platform code read | `modernization-platform` @ `c89aedcb9` |
|
||||
@@ -244,8 +245,8 @@ Exact role lists are confirmed in each server's phase, tested against a real san
|
||||
| D6 | Is `query_resources` in v1? | **Yes, with scope and size limits** | It's the most useful Azure MCP capability for discovery, and the underlying APIs are read-only. The model writes the query, so it needs the boundary check. |
|
||||
| D7 | Are there sandboxes for all three clouds? | **We need one per provider, with an organisation-level structure** | Management group and organisation behaviour can't be tested in a single account. |
|
||||
| D8 | Does discovery look inside Kubernetes clusters (namespaces, deployments, images)? | **Not in v1.** Add it as a later phase | It needs read access granted on each cluster, and private clusters may be unreachable from KAB. |
|
||||
| D9 | Where does Kyndryl's own access to AWS and Google knowledge live? | **Under review.** Options are in [Well-Architected integration](#well-architected-integration) | The platform review showed it can't sit on the discovery servers' vault credential. |
|
||||
| D10 | Should Discovery use Well-Architected guidance, or only Target Architecture? | **Decided: Target Architecture.** Discovery collects findings only | Agreed 2026-10-30. |
|
||||
| D9 | Where does Kyndryl's own access to AWS and Google knowledge live? | **Decided 2026-11-04: nowhere separate.** Guidance is a tool on each provider's discovery server, on the customer's connection, and `cloud-knowledge` is retired. Options were in [Well-Architected integration](#well-architected-integration) | The platform review showed it can't sit on the discovery servers' vault credential. |
|
||||
| D10 | Should Discovery use Well-Architected guidance, or only Target Architecture? | **Decided: Target Architecture.** Discovery collects findings only. **Superseded 2026-11-03** by ALZ-F01 ADR 0014: Discovery runs a Well-Architected review | Agreed 2026-10-30. |
|
||||
| D11 | Are people's names and emails in collected data kept? | **Decided: no, they are anonymised. Finishing this is deferred** | Agreed 2026-10-30, and deferred the same day. See [Later work](#later-work). |
|
||||
|
||||
## 4. Delivery plan
|
||||
|
||||
Reference in New Issue
Block a user