Releases: labring/sealos
v2.0.3
v2.0.1-beta.3
简体中文,老版本
简体中文,kubernetes v1.14.0+
Sealos 2.0
Support kuberentes 1.14.0+ , you needn't keepalived and haproxy anymore!
build a production kubernetes cluster
Quick Start
sealos init --master 192.168.0.2 --master 192.168.0.3 --master 192.168.0.4 --node 192.168.0.5 --user root --passwd your-server-password
Thats all!
Architecture
+----------+ +---------------+ virturl server: 127.0.0.1:6443
| mater0 |<----------------------| ipvs nodes | real servers:
+----------+ |+---------------+ 10.103.97.200:6443
| 10.103.97.201:6443
+----------+ | 10.103.97.202:6443
| mater1 |<---------------------+
+----------+ |
|
+----------+ |
| mater2 |<---------------------+
+----------+
Every node config a ipvs for masters LB.
Then run a lvscare as a staic pod to check realserver is aviliable. /etc/kubernetes/manifests/sealyun-lvscare.yaml
LVScare
This can care your masters ipvs rules.
公众号：
v2.0.1-beta.2
简体中文,老版本
简体中文,kubernetes v1.14.0+
Sealos 2.0
Support kuberentes 1.14.0+ , you needn't keepalived and haproxy anymore!
build a production kubernetes cluster
Quick Start
sealos init --master 192.168.0.2 --master 192.168.0.3 --master 192.168.0.4 --node 192.168.0.5 --user root --passwd your-server-password
Thats all!
Architecture
+----------+ +---------------+ virturl server: 127.0.0.1:6443
| mater0 |<----------------------| ipvs nodes | real servers:
+----------+ |+---------------+ 10.103.97.200:6443
| 10.103.97.201:6443
+----------+ | 10.103.97.202:6443
| mater1 |<---------------------+
+----------+ |
|
+----------+ |
| mater2 |<---------------------+
+----------+
Every node config a ipvs for masters LB.
Then run a lvscare as a staic pod to check realserver is aviliable. /etc/kubernetes/manifests/sealyun-lvscare.yaml
LVScare
This can care your masters ipvs rules.
公众号：
v2.0.1-beta.1
简体中文,老版本
简体中文,kubernetes v1.14.0+
Sealos 2.0
Support kuberentes 1.14.0+ , you needn't keepalived and haproxy anymore!
build a production kubernetes cluster
Quick Start
sealos init --master 192.168.0.2 --master 192.168.0.3 --master 192.168.0.4 --node 192.168.0.5 --user root --passwd your-server-password
Thats all!
Architecture
+----------+ +---------------+ virturl server: 127.0.0.1:6443
| mater0 |<----------------------| ipvs nodes | real servers:
+----------+ |+---------------+ 10.103.97.200:6443
| 10.103.97.201:6443
+----------+ | 10.103.97.202:6443
| mater1 |<---------------------+
+----------+ |
|
+----------+ |
| mater2 |<---------------------+
+----------+
Every node config a ipvs for masters LB.
Then run a lvscare as a staic pod to check realserver is aviliable. /etc/kubernetes/manifests/sealyun-lvscare.yaml
LVScare
This can care your masters ipvs rules.
公众号：
v2.0.1-beta.0
简体中文,老版本
简体中文,kubernetes v1.14.0+
Sealos 2.0
Support kuberentes 1.14.0+ , you needn't keepalived and haproxy anymore!
build a production kubernetes cluster
Quick Start
sealos init --master 192.168.0.2 --master 192.168.0.3 --master 192.168.0.4 --node 192.168.0.5 --user root --passwd your-server-password
Thats all!
Architecture
+----------+ +---------------+ virturl server: 127.0.0.1:6443
| mater0 |<----------------------| ipvs nodes | real servers:
+----------+ |+---------------+ 10.103.97.200:6443
| 10.103.97.201:6443
+----------+ | 10.103.97.202:6443
| mater1 |<---------------------+
+----------+ |
|
+----------+ |
| mater2 |<---------------------+
+----------+
Every node config a ipvs for masters LB.
Then run a lvscare as a staic pod to check realserver is aviliable. /etc/kubernetes/manifests/sealyun-lvscare.yaml
LVScare
This can care your masters ipvs rules.
公众号：
v2.0.0.alpha.9
简体中文,老版本
简体中文,kubernetes v1.14.0+
Sealos 2.0
Support kuberentes 1.14.0+ , you needn't keepalived and haproxy anymore!
build a production kubernetes cluster
Quick Start
sealos init --master 192.168.0.2 --master 192.168.0.3 --master 192.168.0.4 --node 192.168.0.5 --user root --passwd your-server-password
Thats all!
Architecture
+----------+ +---------------+ virturl server: 127.0.0.1:6443
| mater0 |<----------------------| ipvs nodes | real servers:
+----------+ |+---------------+ 10.103.97.200:6443
| 10.103.97.201:6443
+----------+ | 10.103.97.202:6443
| mater1 |<---------------------+
+----------+ |
|
+----------+ |
| mater2 |<---------------------+
+----------+
Every node config a ipvs for masters LB.
Then run a lvscare as a staic pod to check realserver is aviliable. /etc/kubernetes/manifests/sealyun-lvscare.yaml
LVScare
This can care your masters ipvs rules.
公众号：
v2.0.0.alpha.8
简体中文,老版本
简体中文,kubernetes v1.14.0+
Sealos 2.0
Support kuberentes 1.14.0+ , you needn't keepalived and haproxy anymore!
build a production kubernetes cluster
Quick Start
sealos init --master 192.168.0.2 --master 192.168.0.3 --master 192.168.0.4 --node 192.168.0.5 --user root --passwd your-server-password
Thats all!
Architecture
+----------+ +---------------+ virturl server: 127.0.0.1:6443
| mater0 |<----------------------| ipvs nodes | real servers:
+----------+ |+---------------+ 10.103.97.200:6443
| 10.103.97.201:6443
+----------+ | 10.103.97.202:6443
| mater1 |<---------------------+
+----------+ |
|
+----------+ |
| mater2 |<---------------------+
+----------+
Every node config a ipvs for masters LB.
Then run a lvscare as a staic pod to check realserver is aviliable. /etc/kubernetes/manifests/sealyun-lvscare.yaml
LVScare
This can care your masters ipvs rules.
公众号：
v2.0.0-beta.2
简体中文,老版本
简体中文,kubernetes v1.14.0+
Sealos 2.0
Support kuberentes 1.14.0+ , you needn't keepalived and haproxy anymore!
build a production kubernetes cluster
Quick Start
sealos init --master 192.168.0.2 --master 192.168.0.3 --master 192.168.0.4 --node 192.168.0.5 --user root --passwd your-server-password
Thats all!
Architecture
+----------+ +---------------+ virturl server: 127.0.0.1:6443
| mater0 |<----------------------| ipvs nodes | real servers:
+----------+ |+---------------+ 10.103.97.200:6443
| 10.103.97.201:6443
+----------+ | 10.103.97.202:6443
| mater1 |<---------------------+
+----------+ |
|
+----------+ |
| mater2 |<---------------------+
+----------+
Every node config a ipvs for masters LB.
Then run a lvscare as a staic pod to check realserver is aviliable. /etc/kubernetes/manifests/sealyun-lvscare.yaml
LVScare
This can care your masters ipvs rules.
公众号：
v2.0.0-beta.0
简体中文,老版本
简体中文,kubernetes v1.14.0+
Sealos 2.0
Support kuberentes 1.14.0+ , you needn't keepalived and haproxy anymore!
build a production kubernetes cluster
Quick Start
sealos init --master 192.168.0.2 --master 192.168.0.3 --master 192.168.0.4 --node 192.168.0.5 --user root --passwd your-server-password
Thats all!
Architecture
+----------+ +---------------+ virturl server: 127.0.0.1:6443
| mater0 |<----------------------| ipvs nodes | real servers:
+----------+ |+---------------+ 10.103.97.200:6443
| 10.103.97.201:6443
+----------+ | 10.103.97.202:6443
| mater1 |<---------------------+
+----------+ |
|
+----------+ |
| mater2 |<---------------------+
+----------+
Every node config a ipvs for masters LB.
Then run a lvscare as a staic pod to check realserver is aviliable. /etc/kubernetes/manifests/sealyun-lvscare.yaml
LVScare
This can care your masters ipvs rules.
公众号：
v2.0.0-alpha.7
简体中文,老版本
简体中文,kubernetes v1.14.0+
Sealos 2.0
Support kuberentes 1.14.0+ , you needn't keepalived and haproxy anymore!
build a production kubernetes cluster
Quick Start
sealos init --master 192.168.0.2 --master 192.168.0.3 --master 192.168.0.4 --node 192.168.0.5 --user root --passwd your-server-password
Thats all!
Architecture
+----------+ +---------------+ virturl server: 127.0.0.1:6443
| mater0 |<----------------------| ipvs nodes | real servers:
+----------+ |+---------------+ 10.103.97.200:6443
| 10.103.97.201:6443
+----------+ | 10.103.97.202:6443
| mater1 |<---------------------+
+----------+ |
|
+----------+ |
| mater2 |<---------------------+
+----------+
Every node config a ipvs for masters LB.
Then run a lvscare as a staic pod to check realserver is aviliable. /etc/kubernetes/manifests/sealyun-lvscare.yaml
LVScare
This can care your masters ipvs rules.