Sealos is a production-ready Kubernetes distribution that provides a one-stop solution for both public and private cloud. https://sealos.io
APACHE-2.0 License
Bot releases are visible (Hide)
Published by fanux almost 5 years ago
本地拉取:
sealos install --pkg-url dashboard.tar
远程拉取:
sealos install --pkg-url https://github.com/sealstore/dashboard/releases/download/v1.10.0-alpha.0/dashboard.tar
dashboard.tar里包含yaml文件与镜像文件等
[root@iZj6c2ihvsz4y7barissm4Z test]# cat config
LOAD docker load -i image.tar
APPLY kubectl apply -f manifests
DELETE kubectl delete -f manifests
REMOVE sleep 10 && docker rmi -f k8s.gcr.io/kubernetes-dashboard-amd64:v1.10.0
[root@iZj6c2ihvsz4y7barissm4Z test]# ls
config image.tar manifests
把上述三个文件打包
[root@iZj6c2ihvsz4y7barissm4Z test]# tar cvf dashboard.tar config image.tar manifests
Published by fanux almost 5 years ago
本地拉取:
sealos install --pkg-url dashboard.tar
远程拉取:
sealos install --pkg-url https://github.com/sealstore/dashboard/releases/download/v1.10.0-alpha.0/dashboard.tar
dashboard.tar里包含yaml文件与镜像文件等
[root@iZj6c2ihvsz4y7barissm4Z test]# cat config
LOAD docker load -i image.tar
APPLY kubectl apply -f manifests
DELETE kubectl delete -f manifests
REMOVE sleep 10 && docker rmi -f k8s.gcr.io/kubernetes-dashboard-amd64:v1.10.0
[root@iZj6c2ihvsz4y7barissm4Z test]# ls
config image.tar manifests
把上述三个文件打包
[root@iZj6c2ihvsz4y7barissm4Z test]# tar cvf dashboard.tar config image.tar manifests
Published by fanux about 5 years ago
本地拉取:
sealos install --pkg-url dashboard.tar
远程拉取:
sealos install --pkg-url https://github.com/sealstore/dashboard/releases/download/v1.10.0-alpha.0/dashboard.tar
dashboard.tar里包含yaml文件与镜像文件等
[root@iZj6c2ihvsz4y7barissm4Z test]# cat config
LOAD docker load -i image.tar
APPLY kubectl apply -f manifests
DELETE kubectl delete -f manifests
REMOVE sleep 10 && docker rmi -f k8s.gcr.io/kubernetes-dashboard-amd64:v1.10.0
[root@iZj6c2ihvsz4y7barissm4Z test]# ls
config image.tar manifests
把上述三个文件打包
[root@iZj6c2ihvsz4y7barissm4Z test]# tar cvf dashboard.tar config image.tar manifests
Published by fanux about 5 years ago
本地拉取:
sealos install --pkg-url dashboard.tar
远程拉取:
sealos install --pkg-url https://github.com/sealstore/dashboard/releases/download/v1.10.0-alpha.0/dashboard.tar
dashboard.tar里包含yaml文件与镜像文件等
[root@iZj6c2ihvsz4y7barissm4Z test]# cat config
LOAD docker load -i image.tar
APPLY kubectl apply -f manifests
DELETE kubectl delete -f manifests
REMOVE sleep 10 && docker rmi -f k8s.gcr.io/kubernetes-dashboard-amd64:v1.10.0
[root@iZj6c2ihvsz4y7barissm4Z test]# ls
config image.tar manifests
把上述三个文件打包
[root@iZj6c2ihvsz4y7barissm4Z test]# tar cvf dashboard.tar config image.tar manifests
Published by fanux about 5 years ago
v2.0.4
Published by fanux about 5 years ago
wget https://github.com/fanux/sealos/releases/download/$TAG/sealos
chmod +x sealos
cp sealos /usr/bin
$TAG 为git tag
修复1.16.0版本join master bug
Published by fanux about 5 years ago
wget https://github.com/fanux/sealos/releases/download/$TAG/sealos
chmod +x sealos
cp sealos /usr/bin
$TAG 为git tag
支持1.16.0版本,v2.0.5-alpha.6 以下版本不支持1.16.0
Published by fanux about 5 years ago
wget https://github.com/fanux/sealos/releases/download/$TAG/sealos
chmod +x sealos
cp sealos /usr/bin
$TAG 为git tag
支持1.16.0版本,v2.0.5-alpha.6 以下版本不支持1.16.0
Published by fanux about 5 years ago
wget https://github.com/fanux/sealos/releases/download/v2.0.5-alpha.6/sealos
chmod +x sealos
cp sealos /usr/bin
支持1.16.0版本,v2.0.5-alpha.6 以下版本不支持1.16.0
Published by fanux about 5 years ago
v2.0.4
Published by fanux about 5 years ago
Useage:
wget https://github.com/fanux/sealos/releases/download/v2.0.5-alpha.4/sealos
cp sealos /usr/bin
Published by fanux about 5 years ago
v2.0.4
Published by fanux about 5 years ago
v2.0.4
Published by fanux about 5 years ago
v2.0.4
Published by fanux about 5 years ago
Published by fanux about 5 years ago
v2.0.4
Published by fanux over 5 years ago
Published by fanux over 5 years ago
简体中文,老版本
简体中文,kubernetes v1.14.0+
Support kuberentes 1.14.0+ , you needn't keepalived and haproxy anymore!
build a production kubernetes cluster
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!
+----------+ +---------------+ 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
This can care your masters ipvs rules.
Published by fanux over 5 years ago
简体中文,老版本
简体中文,kubernetes v1.14.0+
Support kuberentes 1.14.0+ , you needn't keepalived and haproxy anymore!
build a production kubernetes cluster
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!
+----------+ +---------------+ 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
This can care your masters ipvs rules.
Published by fanux over 5 years ago
简体中文,老版本
简体中文,kubernetes v1.14.0+
Support kuberentes 1.14.0+ , you needn't keepalived and haproxy anymore!
build a production kubernetes cluster
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!
+----------+ +---------------+ 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
This can care your masters ipvs rules.