Hi All,

 

Currently all the routes to the external NW for the Pods is provided through the OAM network with modifications in the IPTables rules and bridges.

But in the prod environment pods talking with external NW should be routed through the data interface and the question here is how can it be achieved with load balancers which are available for bare metal case like MetalLB.

 

See in the attached diagram MetalLB , routes the all the external NW through the OAM interface, I have checked on STX 3.0. For testing it is ok but may not for prod env.

We need something or someway to get it routed through data interface.

 

 

 

In STX4.0, as part of the cert-manager work, we added nginx as the default ingress controller for starlingx.  It’s installed at bootstrap time.

 

We currently don’t support a load balancer for the StarlingX.
Typically in Kubernetes that is provided by the underlying cloud that Kubernetes is installed on ... but we are Kubernetes on bare metal.

There are solutions for bare metal load balancers for Kubernetes, but we haven’t done that yet on StarlingX.

Depending on your end-to-end networking solution, it may not really be necessary.

 

Greg.

 

 

I have a question from  customer.  Is it possible to put run load balancers for StarlingX worker nodes?  Do we support the standard Kubernetes Ingress and Ingress Controller features?

 

        brucej