You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For most Networking related issues, there are two levels available for networking observability
68
+
-[Container Network Metrics][aks-container-metrics] (default): Allows for node level metrics
69
+
-[Advanced Container Network Metrics][advanced-container-network-metrics]: In addition to node level metrics, you can also observe pod-level metrics including FQDN metrics for troubleshooting.
70
+
67
71
### Pod Connectivity Problems
68
72
69
73
**Symptoms**: Pods can't communicate with other pods or external services.
@@ -219,6 +223,7 @@ nc -zv 10.0.0.10 53
219
223
- Check that Karpenter nodes can reach the service subnet
220
224
- Restart CoreDNS pods if they're in error state: `kubectl rollout restart deployment/coredns -n kube-system`
221
225
- Verify NSG rules allow traffic on port 53 (TCP/UDP)
226
+
- Run a connectivyt analysis with the [Azure Virtual Network Verifier][connectivity-tool] tool to validate outbound connectivity
222
227
223
228
## Azure-Specific Issues
224
229
@@ -272,4 +277,7 @@ az vm list-usage --location <region> --query "[?currentValue >= limit]"
0 commit comments