aks-cost-optimization

原文涵盖的主题

• AKS Cost Optimization
• When to Use This Skill
• MCP Tools
• Workflow/Steps
• Error Handling

Use for advanced existing-cluster analysis requiring scheduling, placement, or verified storage mapping. Route overall AKS cost assessments to azure-kubernetes, spend/anomalies to cost-analysis, commitments to cost-optimization, and incidents to aks-troubleshooting when those skills are available. When called from an overall assessment, return findings for its ranked report. Prefer fitting Azure MCP reads. Never invent tools or use az/kubectl without approved shell access and a target-bound context. 1. Bind the subscription, cluster, resource group, and kube context. 2. Route to NAP readiness, bin-packing, node-scaling bottlenecks, or storage optimization. 3. When invoked for AKS commitment context, use the commitment-demand handoff and return demand evidence without benefit analysis or a transaction. 4. Keep reads non-mutating; require approval for every change. Missing capability: analyze supplied evidence or provide a collection plan; mark dependent cost or commitment results unavailable. Evidence conflict: mark the conclusion unconfirmed.