Dev/039 aks enterprise

[Ryan Peters (ryanpeters-MSFT)]

This pull request updates the AKS Enterprise Grade workshop to modernize networking, ingress, and access patterns, focusing on Azure CNI Overlay networking and AKS-managed Istio ingress with Gateway API. It revises both the public and private cluster solutions, removing legacy NGINX ingress and kubenet guidance, and adds detailed instructions for using Azure Bastion native client tunneling for private cluster access. The documentation and deployment scripts are streamlined for clarity and to match current Azure recommendations.

Networking and Ingress Modernization

• Switches networking guidance from Azure CNI vs. kubenet to Azure CNI Overlay, clarifying pod IP allocation and recommending migration for legacy clusters. [1] [2]
• Replaces NGINX ingress controller instructions with AKS-managed Istio ingress using Gateway API, updating deployment and access steps accordingly. [1] [2] [3]
• Updates AKS cluster creation commands to use --network-plugin-mode overlay and enable Gateway API and Istio app routing add-ons by default for both public and private clusters. [1] [2]

Access and Connectivity Improvements

• Adds comprehensive instructions for using Azure Bastion's native client tunneling to access private AKS clusters, reducing reliance on jump VMs and clarifying connectivity limitations. [1] [2]
• Updates documentation to reflect Bastion-based access as the primary method, with the jump VM path now optional and clearly separated. [1] [2]

Documentation and Usability Enhancements

• Clarifies the role of the managed Gateway as the sole public LoadBalancer, with web/API services using ClusterIP on port 8080. [1] [2]
• Updates port mappings and browser access instructions for container and ACI deployments to match new service ports. [1] [2]
• Updates firewall rule naming for clarity and aligns with new ingress solution.
• Adds a new .devcontainer.json for Codespaces/Dev Containers with appropriate tools and extensions for the updated workshop.

These updates ensure the workshop is aligned with current Azure best practices and provide a smoother, more secure experience for both public and private AKS cluster scenarios.