biaogao

Hi @mhsh64 , correct, right now AGIC doesn't support[ multiple IPs on the same port](https://github.com/Azure/application-gateway-kubernetes-ingress/blob/master/docs/annotations.md#use-private-ip).

Hi @mhsh64 , AGIC support for the feature is definitely on our roadmap, but we don't have ETA for it given appgw itself doesn't support it now. To deploy two...

Hi @mhsh64 , In the next release version(including rc), AGIC will support to delegate two ingress resources in the same namespace to two different controllers.

Thanks @mhsh64 , that's exactly the feature we will release soon to make the ingress class configurable.

Hi @ezYakaEagle442 , there is a [note ](https://github.com/Azure/application-gateway-kubernetes-ingress/blob/master/docs/annotations.md#use-private-ip) indicating that "App Gateway doesn't support multiple IPs on the same port"

Hi @adamcarter81 , it looks like your issue happens when appgw talks to istio gateway via TLS. with the version of AGIC you are using(1.0.0), AGIC only support `https` when...

Hi @adamcarter81 , could you please help describe the pod? thanks!

Thanks a lot @adamabmsft , did you specify scheme in your container readiness probe definition? would you mind to share your template.spec.containers in your k8s deployment?

Hi @adamcarter81 , [you could only probe the port exposed on your container](https://github.com/Azure/application-gateway-kubernetes-ingress/blob/master/docs/features/probes.md), if you specify the backend protocol https, then you will need to use port 443

Hi @adamcarter81 , Thanks for clarification. `If so, why does exposing the pod to AGIC work, this has the same readiness probe: kubectl describe pod server-deployment-8485574dc9-7p4zp -n test Port: 443/TCP...