Add hyperscaler discovery MCP servers and Well-Architected guidance
Some checks failed
check agents / check (push) Failing after 12s

azure-discovery, aws-discovery and gcp-discovery collect read-only metadata
on servers, workloads, Kubernetes clusters, networks, data stores, policies
and provider recommendations. Credentials arrive per call from the vault.
Replies are paged, scrubbed of secrets and anonymised, and throttled calls
back off. cloud-knowledge searches each provider's Well-Architected guidance
from fixed lists only, so no customer detail can leave the platform.

Adds shared skills, the render and test tooling, a public Python Dockerfile
until the hardened base image is reachable, the customer access guide, the
implementation plan and the Vault Service platform issue.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
2026-10-30 20:11:57 +00:00
parent 416c66ced4
commit c14a94f33b
91 changed files with 13296 additions and 1 deletions

View File

@@ -0,0 +1,25 @@
apiVersion: v1
kind: ConfigMap
metadata:
name: <placeholder_for_mcp_server_name>-config # Do not modify, this will be replaced during deployment by the CI/CD pipeline
data:
# Read by the CI/CD pipeline: the server's name, and the port it listens on
# (used for the container, the Service and the probes)
MCP_SERVER_NAME: "cloud-knowledge"
SERVER_PORT: "8114"
# One JSON object per line; LOG_FORMAT=console prints readable lines
LOG_LEVEL: "INFO"
LOG_FORMAT: "json"
# Leave on. The Gateway authenticates to this server with a bearer token, and
# turning this off makes every tool callable by anything that can reach the
# pod inside the cluster.
REQUIRE_AUTH: "true"
# Refuse a call that arrives without the tenant's credential from the Vault Service
REQUIRE_VAULT_CONNECTION: "true"
# Add your own settings here
# EXAMPLE_SETTING: "value"