📚 Documentation needed for commit test

[github-actions]

Summary

Commit 19f074ef introduces a significant infrastructure component — deploying the AKS MCP Server via Helm with Azure Workload Identity — that requires documentation updates.

What Changed

infra/aks-mcp.tf

New helm_release resource (aks_mcp) that:

• Pulls the aks-mcp Helm chart from oci://ghcr.io/azure/aks-mcp/charts
• Reuses the pre-created workload identity Service Account from kubernetes.tf
• Sets pod label azure.workload.identity/use: true for federated token pickup
• Injects AZURE_CLIENT_ID and AZURE_TENANT_ID as environment variables
• Exposes service on port 8000, matching .copilot/mcp-config.json

infra/outputs.tf

New Terraform output aks_mcp_port_forward_command:

kubectl port-forward -n aks-mcp svc/aks-mcp 8000:8000

Why Documentation Is Needed

• New integration: AKS MCP Server via Helm chart from GHCR
• Architectural change: new service added to the AKS cluster
• Security config: Azure Workload Identity / federated credentials
• Developer-facing procedure: port-forward command needed for local MCP access

Suggested Documentation Updates

1. README.md or infra/README.md — Add section on the AKS MCP Server: what it is, how Workload Identity authenticates it, the port-forward command, and the relationship to .copilot/mcp-config.json.
2. infra/ docs — Document the aks_mcp_chart_version Terraform variable.
3. .copilot/ docs — Note that localhost:8000 depends on the port-forward being active before using MCP tooling locally.

No Breaking Changes

This is an additive infrastructure change. However, developers need to run the port-forward command before using MCP tooling locally.

References

• Commit: 19f074efb950f019670ee47ebfa36240476a0b7e
• Files changed: infra/aks-mcp.tf, infra/outputs.tf
• Helm chart: oci://ghcr.io/azure/aks-mcp/charts/aks-mcp