Akshay Gupta

@renancnetto Thanks for the proposal. Annotation names look good.

@melzayet Thanks for pointing out. This looks like a bug in AGIC in the following line: https://github.com/Azure/application-gateway-kubernetes-ingress/blob/b875ca5514f335930650db5099a4f8c74fc8cfaa/pkg/k8scontext/context.go#L944 It also needs to compare the controller's name along with the controller type....

@eduardodfmex Is your Application Gateway up and running or is it being created as part of this? If it is only update, then it seems to be an Application Gateway...

@NiklasArbin I took a quick look and found that update was delayed as there was a platform upgrade in progress.

@danielnagyyy please feel free to create a support ticket. We can take a look at the gateway.

@CJJ69 Thank for sharing! Will straight away get to fixing this.

@thisispaulsmith can you also add `host` in the rules as well. Example: ```yaml ... tls: - hosts: - testing.domain.com secretName: testing-tls rules: - host: testing.domain.com http: paths: - path: /testpath...

Try specifying ```yaml appgw.ingress.kubernetes.io/backend-protocol: "https" ``` https://github.com/Azure/application-gateway-kubernetes-ingress/blob/master/docs/annotations.md#backend-protocol

@marc-mueller Can you please check if the prohibited target is being picked by AGIC by checking the logs ? Also, can you upgrade the installation to 1.2.0 ?

This will require leader election support on AGIC as multiple AGIC pod will cause multiple updates on AppGW. Appendix: [K8s docs](https://v1-17.docs.kubernetes.io/blog/2016/01/simple-leader-election-with-kubernetes/) [Example PR](https://github.com/Azure/aad-pod-identity/commit/1aa529b86ee0c3c1ad1a21c52f74bfac14d23db6)