Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

When using managed Kubernetes clusters in the cloud (Azure, AWS, Google) the Kubernetes ingress controller(s) can create and/or communicate with the load balancer(s) of the respective cloud provider. This connection between the ingress controller and the cloud load balancer ensures that the cloud load balancer routes the traffic to the cluster nodes where the ingress controllers are running on. It also ensures distribution of the traffic between these cluster nodes according to the rules available on the cloud’s load balancers.

...

Expand
titleExpanded Draw.io diagram view with the standard Confluence view.
Drawio
zoom1
simple0
inComment0
pageId1588592658
custContentId1588789937
lbox1
diagramDisplayNameLoadbalancer and Kubernetes
contentVer10
revision10
baseUrlhttps://vidispine.atlassian.net/wiki
diagramNameLoadbalancer and Kubernetes
pCenter0
width1098
links
tbstyle
height603

...

  • Failover from one node to another may take up to 10 seconds. During this time the system is not reachable.

  • As the LB virtual IP always points to a single node there is no load balancing taking place. Only failover in case of a node failure is ensured.

...

Expand
titleDraw.io diagram view with the standard Confluence view.
Drawio
zoom1
simple0
inComment0
pageId1588592658
custContentId1588725267
lbox1
diagramDisplayNameMetalLB Layer 2
contentVer7
revision7
baseUrlhttps://vidispine.atlassian.net/wiki
diagramNameMetalLB Layer 2
pCenter0
width1120
links
tbstyle
height603

MetalLB BGP Mode

How It Works

...

...

Expand
titleDraw.io diagram view with the standard Confluence view.
Drawio
zoom1
simple0
inComment0
pageId1588592658
custContentId1588725278
lbox1
diagramDisplayNameMetalLB BGP
contentVer5
revision5
baseUrlhttps://vidispine.atlassian.net/wiki
diagramNameMetalLB BGP
pCenter0
width1098
links
tbstyle
height603

Further Reading