1# AKS Command Flows
2 
3## Cluster Baseline Flow
4 
5```text
6Resolve subscription -> resolve resource group -> resolve cluster -> inspect cluster state -> inspect node pools -> inspect resource health -> inspect recent operations
7```
8 
9CLI fallback when AKS-MCP cannot perform the cluster baseline read:
10 
11```bash
12az aks show -g <resource-group> -n <cluster-name>
13az aks nodepool list -g <resource-group> --cluster-name <cluster-name>
14az monitor activity-log list -g <resource-group> --max-events 20
15```
16 
17## Kubernetes Baseline Flow
18 
19```text
20Check API reachability -> inspect nodes -> inspect kube-system -> inspect events -> inspect affected namespace -> inspect pod details and logs
21```
22 
23CLI fallback when AKS-MCP cannot perform the Kubernetes baseline read:
24 
25```bash
26kubectl cluster-info
27kubectl get nodes -o wide
28kubectl get pods -n kube-system
29kubectl get events -A --sort-by=.lastTimestamp
30kubectl get pods -n <namespace>
31kubectl describe pod <pod-name> -n <namespace>
32kubectl logs <pod-name> -n <namespace> --previous
33```
34 
35## Connectivity Flow
36 
37```text
38pod -> service -> endpoints -> ingress or load balancer -> DNS -> network controls
39```
40 
41CLI fallback when AKS-MCP cannot perform the connectivity read:
42 
43```bash
44kubectl get pods -n <namespace> -o wide
45kubectl get svc -n <namespace>
46kubectl get endpoints -n <namespace>
47kubectl get ingress -n <namespace>
48kubectl describe ingress <ingress-name> -n <namespace>
49```
50 
51## Detector Flow
52 
53```text
54resolve cluster resource ID -> list detectors or choose category -> select a focused time window -> run the detector or category -> rank critical findings above warnings -> ignore emerging issues when choosing the primary root cause
55```
56 
57## Monitoring Flow
58 
59```text
60check resource health -> inspect metrics -> verify diagnostics settings -> inspect control plane logs if available -> correlate with Application Insights or namespace symptoms
61```
62 
63## Scheduling Flow
64 
65```text
66pod events -> node capacity -> taints and tolerations -> affinity rules -> PVC state -> quotas
67```
68 
69CLI fallback when AKS-MCP cannot perform the scheduling read:
70 
71```bash
72kubectl describe pod <pod-name> -n <namespace>
73kubectl get nodes -o wide
74kubectl describe node <node-name>
75kubectl get pvc -n <namespace>
76kubectl describe quota -n <namespace>
77```
78 
79## Safety Boundary
80 
81Treat the following as change operations and avoid them unless the user explicitly asks for remediation:
82 
83- deleting or restarting pods
84- cordon and drain operations
85- scaling workloads or node pools
86- cluster upgrade operations
87- DNS, route, NSG, or firewall changes
88