1
1
---
2
2
title : Network Loadbalancer
3
3
4
- oep -number : 3
4
+ iep -number : 3
5
5
6
6
creation-date : 2022-10-18
7
7
@@ -21,16 +21,19 @@ reviewers:
21
21
22
22
---
23
23
24
- # OEP -3: Network Loadbalancer
24
+ # IEP -3: Network Loadbalancer
25
25
26
26
## Table of Contents
27
27
28
- - [ Summary] ( #summary )
29
- - [ Motivation] ( #motivation )
28
+ - [ IEP-3: Network Loadbalancer] ( #IEP-3-network-loadbalancer )
29
+ - [ Table of Contents] ( #table-of-contents )
30
+ - [ Summary] ( #summary )
31
+ - [ Motivation] ( #motivation )
30
32
- [ Goals] ( #goals )
31
33
- [ Non-Goals] ( #non-goals )
32
34
- [ Details] ( #details )
33
- - [ Proposal] ( #proposal )
35
+ - [ Proposal] ( #proposal )
36
+ - [ Routing State Object] ( #routing-state-object )
34
37
35
38
## Summary
36
39
@@ -43,7 +46,7 @@ load balancers, since they can be used as a foundation for the higher level load
43
46
44
47
## Motivation
45
48
46
- A ` VirtualIP ` ([ OEP -1] ( 01-networking-integration.md#the-virtualip-type ) ) allows to expose a ` NetworkInterface `
49
+ A ` VirtualIP ` ([ IEP -1] ( 01-networking-integration.md#the-virtualip-type ) ) allows to expose a ` NetworkInterface `
47
50
with a stable public IP. Services running on a ` Machine ` using that ` NetworkInterface ` can be consumed this way.
48
51
However, if the ` Machine ` or the service running on that ` Machine ` crashes, the service will have an outage.
49
52
To be more resilient and to scale beyond single ` NetworkInterface ` s, a ` LoadBalancer ` allows targeting multiple
@@ -55,7 +58,7 @@ To be more resilient and to scale beyond single `NetworkInterface`s, a `LoadBala
55
58
- Load balancers should allow specifying their IP stack (` IPv4 ` / ` IPv6 ` / dual stack). Public IP addresses
56
59
should be allocated according to the specified IP stack.
57
60
- Load balancers should support multiple target ` NetworkInterface ` s (
58
- see ([ OEP -1] ( 01-networking-integration.md#the-networkinterface-type ) )
61
+ see ([ IEP -1] ( 01-networking-integration.md#the-networkinterface-type ) )
59
62
- The load balancer should dynamically watch for target ` NetworkInterface ` s.
60
63
- All target ` NetworkInterface ` s must be in the same ` Network ` .
61
64
- The load balancer should be able to filter unwanted traffic. The filtering must not alter the packages.
@@ -87,7 +90,7 @@ its `status.ips`.
87
90
` ports ` defines an allow list of which traffic should be handled by a ` LoadBalancer ` . A ` port ` consists of
88
91
a ` protocol ` , ` port ` and an optional ` portEnd ` to support port range filtering.
89
92
` networkRef ` defines the target ` Network ` a ` NetworkInterface ` has to be in in order to be an eligible target
90
- for traffic forwarding (see [ OEP -1] ( 01-networking-integration.md#the-networkinterface-type ) ).
93
+ for traffic forwarding (see [ IEP -1] ( 01-networking-integration.md#the-networkinterface-type ) ).
91
94
92
95
[ // ] : # ( @formatter:off )
93
96
``` yaml
0 commit comments