You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Morning all, at my company we're trying a two ingress-controller setup:
A private ingress controller for internal traffic and a public one for public facing/external traffic.
We've set up these two apisix-ingress-controllers on eks, so far so good. We're having some issues with the CRDs: it seems that the private controller picks up all the CRDs, even ones meant for the public one.
Is there a way to apply a filter to the CRDs or direct them to a specific ingress controller, besides namespace filtering? Looking at the documentation, chart and templates I couldn't find much.
Morning all, at my company we're trying a two ingress-controller setup:
A private ingress controller for internal traffic and a public one for public facing/external traffic.
We've set up these two apisix-ingress-controllers on eks, so far so good. We're having some issues with the CRDs: it seems that the private controller picks up all the CRDs, even ones meant for the public one.
Is there a way to apply a filter to the CRDs or direct them to a specific ingress controller, besides namespace filtering? Looking at the documentation, chart and templates I couldn't find much.
Thanks in advance.
Kubernetes version: v1.28.6-eks-508b6b3
Chart version: 2.6.0
Application version: 3.8.0
ingress config if it helps.
NOTE: we have both service.type LoadBalancer and ingress-controller.gateway.type LoadBalancer otherwise externaldns doesn't work, apparently.
The text was updated successfully, but these errors were encountered: