request help: Support for Separate Ingress Classes for Public and Private DNS Zones in AWS EKS

[MichaelLLC]

Issue description

I have deployed an AWS EKS cluster and created two DNS zones: one private and one public. I need to deploy Apache APISIX with two separate ingress classes, where each ingress controller processes rules only for its respective DNS zone.

Public Requests: Should be handled by apisix-external.
Private/Internal Requests: Should be handled by apisix-internal.
I am using ApisixRoute CRDs to define the rules, and it is crucial to separate the rules for each APISIX instance to ensure proper routing.

Environment

• your apisix-ingress-controller version (output of apisix-ingress-controller version --long): 1.8
• your Kubernetes cluster version (output of kubectl version): 1.29
• if you run apisix-ingress-controller in Bare-metal environment, also show your OS version (uname -a):