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
When following the public/private docs using nginx-ingress-controller then the implementation is well understandable (and was also relevant when using --annotation-filter flag).
This approcah required the installation of both internal and external nginx controller, since the contoller would create an actual LB in AWS that acts as the gateway to the cluster.
using ALB controller there is no pre defined LB in aws, but each application can created its own LB, it can be either internal, or internet facing, using a single ingress class,
using the --ingress-class flag, there is no way of distinguish internal/internel facing types, and actually forces me to create two different ALB controllers, although its not really needed.
while using the --annotation-filter flag, there were no issues, but its now deprecated.
what is the best practice approach here?
keep using 2 alb controllers?
keep using 1 alb controller, but also use the deprecated flag?
What would you like to be added:
external DNS documentation for ALB controller using public/private records
Why is this needed:
There is no way of using a single ALB controller, using the new --ingress-class similar to the --annotation-filter flag
The text was updated successfully, but these errors were encountered:
When following the public/private docs using nginx-ingress-controller then the implementation is well understandable (and was also relevant when using
--annotation-filter
flag).This approcah required the installation of both internal and external nginx controller, since the contoller would create an actual LB in AWS that acts as the gateway to the cluster.
using ALB controller there is no pre defined LB in aws, but each application can created its own LB, it can be either internal, or internet facing, using a single ingress class,
using the
--ingress-class
flag, there is no way of distinguish internal/internel facing types, and actually forces me to create two different ALB controllers, although its not really needed.while using the
--annotation-filter
flag, there were no issues, but its now deprecated.what is the best practice approach here?
keep using 2 alb controllers?
keep using 1 alb controller, but also use the deprecated flag?
What would you like to be added:
external DNS documentation for ALB controller using public/private records
Why is this needed:
There is no way of using a single ALB controller, using the new
--ingress-class
similar to the--annotation-filter
flagThe text was updated successfully, but these errors were encountered: