This is an ingress controller that can be run on Azure Kubernetes Service (AKS) to allow an Azure Application Gateway to act as the ingress for an AKS cluster.
Describe the bug
Application Gateway is now offering TCP/TLS proxy, eg. for connecting to DB instances (link). Similar, this functionality can be used to access cluster-hosted dbs (statefulsets) using APP GW's private FE, but AGIC annotations do not include that.
Also, the same is missing for health-checks. There is no such annotation like appgw.ingress.kubernetes.io/health-probe-protocol, which would allow to set custom health probe protocol. This is a must-have when using APP GW with TCP PROXY.
To Reproduce
Configure ingress using TCP/TLS protocol, instead of HTTP(S).
Describe the bug Application Gateway is now offering TCP/TLS proxy, eg. for connecting to DB instances (link). Similar, this functionality can be used to access cluster-hosted dbs (statefulsets) using APP GW's private FE, but AGIC annotations do not include that.
Also, the same is missing for health-checks. There is no such annotation like
appgw.ingress.kubernetes.io/health-probe-protocol, which would allow to set custom health probe protocol. This is a must-have when using APP GW with TCP PROXY.To Reproduce Configure ingress using TCP/TLS protocol, instead of HTTP(S).
Ingress Controller details
Image: mcr.microsoft.com/azure-application-gateway/kubernetes-ingress:1.7.4