Thanks for the wonderful learning. If possible please make a video to automate the same using Terraform for different env's like dev,preord and prod envs.
Thanks for the video, i have a doubt, if you existing App gateway configuration is replaced by AGIC means it will be an impact to your existing applications,. In this case how can we use the existing app gateway additionaly as an AGIC for AKS, that means I will be using same app gateway for another applications and wanted to use it for AKS as well.
When you're using an existing Azure Application Gateway (App Gateway) and want to enable AGIC for AKS, it requires some careful planning to avoid impacting the existing applications. 1.Check the Existing Configuration: Review the current setup of your App Gateway to understand the listener, rules, and backend pool configurations for your existing applications. This will help ensure you don’t disrupt these while adding AKS-related settings. 2.Create a New Listener for AKS: In your App Gateway, create a new listener specifically for AKS traffic. This new listener will not interfere with your existing listeners and rules. Assign a different port for AKS traffic if necessary. If your applications are using the default HTTP/HTTPS ports (80/443), you may need to configure unique paths or use another domain/subdomain for the AKS services. 3.Update Backend Pool for AKS: Create a separate backend pool in the App Gateway for AKS services. You can configure the AGIC to point to the new backend pool for routing traffic to your AKS cluster. Ensure that this backend pool is separate from the one used by your existing applications. 4. Use Path-Based Routing: If you want to share the same listener for both AKS and other applications, configure path-based routing. 5.Enable AGIC with Existing App Gateway Deploy AGIC to your AKS cluster, specifying your existing App Gateway as the gateway to manage. AGIC will configure routes for the services running in your AKS cluster, ensuring it only manages the resources related to AKS and does not modify existing routes and configurations for other applications.
Thankyou for the Awesome Video !! You made the learning easy
Thanks Man🎉 I really appreciate ur work. Pls continue this series with some practical AKS concepts
Thanks for the wonderful learning. If possible please make a video to automate the same using Terraform for different env's like dev,preord and prod envs.
Great suggestion!
Thanks for the video, i have a doubt, if you existing App gateway configuration is replaced by AGIC means it will be an impact to your existing applications,. In this case how can we use the existing app gateway additionaly as an AGIC for AKS, that means I will be using same app gateway for another applications and wanted to use it for AKS as well.
When you're using an existing Azure Application Gateway (App Gateway) and want to enable AGIC for AKS, it requires some careful planning to avoid impacting the existing applications.
1.Check the Existing Configuration:
Review the current setup of your App Gateway to understand the listener, rules, and backend pool configurations for your existing applications. This will help ensure you don’t disrupt these while adding AKS-related settings.
2.Create a New Listener for AKS:
In your App Gateway, create a new listener specifically for AKS traffic. This new listener will not interfere with your existing listeners and rules.
Assign a different port for AKS traffic if necessary. If your applications are using the default HTTP/HTTPS ports (80/443), you may need to configure unique paths or use another domain/subdomain for the AKS services.
3.Update Backend Pool for AKS:
Create a separate backend pool in the App Gateway for AKS services. You can configure the AGIC to point to the new backend pool for routing traffic to your AKS cluster.
Ensure that this backend pool is separate from the one used by your existing applications.
4. Use Path-Based Routing:
If you want to share the same listener for both AKS and other applications, configure path-based routing.
5.Enable AGIC with Existing App Gateway
Deploy AGIC to your AKS cluster, specifying your existing App Gateway as the gateway to manage.
AGIC will configure routes for the services running in your AKS cluster, ensuring it only manages the resources related to AKS and does not modify existing routes and configurations for other applications.