"git@git.gitsec.cn:baidan/sealos.git" did not exist on "96fe90a755675dbd6175d996cf40966e1765dbb9"
user avatar
add wait for cert
fanux authored
96fe90a7
Name Last commit Last update
Godeps add vendor
cmd coding finished
install add wait for cert
vendor add vendor
.drone.yml add
.gitignore add vendor
Dockerfile add
LICENSE add
Note.md add .drone and note
README.md add readme
main.go add

Awesome Build Status

简体中文,老版本 简体中文,kubernetes v1.14.0+

离线包购买市场

sealos 1.x docs

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.

公众号:

sealyun