# Vault Service isn't deployed on the KAB dev cluster | | | |---|---| | Date | 2026-10-30 | | Environment | KAB dev (`crucible-kab-dev-aks`) | | Severity | High. No credential can reach an MCP server through the gateway | | Status | Open; needs the platform deployment's owner | ## Summary The Credentials page reports that the Vault Service could not be reached, because the service doesn't exist on this cluster. MCP servers that need a stored connection can't be used through the gateway, and that includes every hyperscaler discovery server. ## Evidence - No Deployment or Service matching `vault` in any namespace. - No vault service image in `cruciblecoredevacr`. - No vault settings in the plain environment of the API or the MCP gateway. - The API falls back to its default, `http://agent-builder-vault-service:8200` (`agent-builder-api/src/api/vault_routes.py`), and returns 503 when that fails. ## What turning it on needs 1. A vault service image available to the cluster. 2. An Azure Key Vault for tenant credentials: the `tenant_credentials_key_vault` Terraform module, gated by `enable_tenant_credentials_key_vault`. 3. An identity for the service with Key Vault Secrets Officer on that vault (`vault_service_principal_id`, or workload identity through `vault_service_account_name`). 4. `global.vaultService.enabled` set on the `kyn` Helm release, so that the API and gateway agree, with `VAULT_PROVIDER` set. The AKS chart ships the `agent-builder-vault-service` subchart. This is from reading the chart and Terraform, and hasn't been tried. ## Workaround For a trial only, a connection can be sent straight to a deployed server's `/messages` endpoint in `params._meta`, bypassing the gateway. That's how `azure-discovery` was tested on 2026-10-30. It proves the server against Azure, and doesn't prove the vault or gateway path.