bowei / application-gateway-kubernetes-ingress Goto Github PK

The Application Gateway Ingress Controller allows the Azure Application Gateway to be used as the ingress for an Azure Kubernetes Service aka AKS cluster. As shown in the figure below, the ingress controller runs as a pod within the AKS cluster. It consumes Kubernetes Ingress Resources and converts them to an Azure Application Gateway configuration which allows the gateway to load-balance traffic to Kubernetes pods.

Refer to the installation instructions to install the ingress controller on an AKS cluster.

Refer to the tutorials to understand how you can expose an AKS service over HTTP or HTTPS, to the internet, using an Azure Application Gateway.

The best way to report an issue is to create a Github Issue for the project. Please include the following information when creating the issue:

• Subscription ID for AKS cluster.
• Subscription ID for Application Gateway.
• AKS cluster name/ARM Resource ID.
• Application Gateway name/ARM Resource ID.
• Ingress resource definition that might causing the problem.
• The Helm configuration used to install the ingress controller.

This is a Golang project. You can find the build instructions of the project in the Developer Guide.

This project welcomes contributions and suggestions. Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, visit https://cla.microsoft.com.

When you submit a pull request, a CLA-bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (e.g., label, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repos using our CLA.

This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact [email protected] with any additional questions or comments.