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
{{ message }}
This repository was archived by the owner on Feb 27, 2022. It is now read-only.
Copy file name to clipboardExpand all lines: README.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,15 +2,15 @@
2
2
A tcp load balancer that is aware of multiple OpenShift clusters and their exported routes. Also uses pod filters to determine where a HA-Proxy is running.
3
3
4
4
## Screenshot
5
-

5
+

6
6
7
7
## Main idea
8
8
In a large, high load production OpenShift cluster changes to cluster itself impose a huge risk.
9
9
During two years of OpenShift operating experience the idea of a rolling update model for the hole OpenShift cluster formed.
10
10
Basically this works the same way the rolling update of an application on OpenShift works.
11
11
But instead of creating new containers, you create a hole new OpenShift cluster and automatically migrate the applications based on any selectors.
12
12
13
-

13
+

14
14
15
15
In our case we would like to move less important projects to the new cluster, test all operations in productive workload and then migrate the important apps.
16
16
As everything is containerized and based on yaml configuration files, the migration of applications is quite easy.
@@ -24,10 +24,10 @@ The load balancer was created as a prototype for my thesis during my masters deg
24
24
25
25
26
26
## Smart load balancer components
27
-

27
+

0 commit comments