Outline:
Mastering AKS Troubleshooting #2: VNet Cross-Connectivity and Port Resolution
Introduction
• Overview of AKS Troubleshooting • Goal of this blog postTroubleshooting Cross-Connectivity and Port Resolution
• Understanding the architecture • Identifying the source of the problem • Troubleshooting stepsTroubleshooting with Azure CLI
• Prerequisites • Using Azure CLI to diagnose the issue • Using Azure CLI to debug the issueCommon Problems
• Network Security Group (NSG) rules • Subnet ACLs • VNet peering settingsTroubleshooting with Azure Portal
• Using Azure Portal to diagnose the issue • Using Azure Portal to debug the issueTroubleshooting with kubectl
• Prerequisites • Using kubectl to diagnose the issue • Using kubectl to debug the issueCommon Issues
• K8s services • K8s deployments • K8s podsTroubleshooting Tips and Tricks
• Using relevant resources • Checking Azure Activity Logs • Using diagnostic settingsConclusion
• Summary • Further resourcesPopular Questions
1. What is AKS Troubleshooting?
2. How do I troubleshoot VNet cross-connectivity and port resolution?
3. What are the prerequisites for using Azure CLI and kubectl?
4. What are the common problems for Network Security Group (NSG) rules, Subnet ACLs, and VNet peering settings?
5. What tips and tricks can I use for troubleshooting?
