In setups with Traefik Ingressroutes, a LoadBalancer is deployed by Traefik. When Cuber installs its own one next to it, is is ignored as long as the one that is already active has bound the external ports already. As soon as Traefik is restarted however, the dormant Cuber managed LoadBalancer pops to life which leads to all IngressRoutes being ignored.
Setting ingress: true in the Cuberfile leads to an Ingress living next to the Ingressroutes which then acts as a default catch for all requests that are not matched by Traefik, which is dangerous in case certain paths are protected by middlewares Ingressroutes rules.
For such setups, the only sane thing is not to touch the ingress side at all and deploy neither a LoadBalancer nor an Ingress, but there is currently no option to do that. Could that be added?
In setups with Traefik Ingressroutes, a
LoadBalanceris deployed by Traefik. When Cuber installs its own one next to it, is is ignored as long as the one that is already active has bound the external ports already. As soon as Traefik is restarted however, the dormant Cuber managedLoadBalancerpops to life which leads to allIngressRoutesbeing ignored.Setting
ingress: truein theCuberfileleads to anIngressliving next to theIngressrouteswhich then acts as a default catch for all requests that are not matched by Traefik, which is dangerous in case certain paths are protected by middlewaresIngressroutesrules.For such setups, the only sane thing is not to touch the ingress side at all and deploy neither a
LoadBalancernor anIngress, but there is currently no option to do that. Could that be added?