Multiple kong-ingress-controller compete to taking over of the ingress process and communication with cert-manager

Hi @hbagdi thanks for take your time to read.

How to can I configure my ingress resource to listen to different class? I am using this class kubernetes.io/ingress.class: "kong" which point to kong-ingress-controller, this is a standard annotation, I think so, but how to can I differentiate one kong instance of other?

This means, I want to use multiple kong-ingress-controllers how to can I point to one kong in my ingress resource and other kong in other ingress resource?