kubecon 宣传册

[fanux]

宣传册素材

[fanux]

sealos app store

[fanux]

[fanux]

[fanux]

Arch

[fanux]

[fanux]

Core features

• Manage clusters lifecycle
  • Quickly install HA Kubernetes clusters
  • Add / remove nodes
  • Clean the cluster, backup and auto recovering, etc.
• Download and use OCI-compatible distributed applications
  • OpenEBS, MinIO, Ingress, PostgreSQL, MySQL, Redis, etc.
• Customize you own distributed applications
  • Using Dockerfile to build distributed applications images, saving all dependencies.
  • Push distributed applications images to Docker Hub.
  • Combine multiple applications to build your own cloud platform.
• Sealos cloud
  • Run any distributed applications
  • Have a full public cloud capability，and run it anywhere

Cluster lifecycle

Init kubernetes cluster

$ sealos run labring/kubernetes:v1.25.0 labring/calico:v3.24.1 \
     --masters 192.168.64.2,192.168.64.22,192.168.64.20 \
     --nodes 192.168.64.21,192.168.64.19 -p [your-ssh-passwd]

Parameter name	Parameter value example	Parameter description
--masters	192.168.0.2	kubernetes master node address list
--nodes	192.168.0.3	kubernetes node node address list
--ssh-passwd	[your-ssh-passwd]	ssh login password
image	kubernetes:v1.25.0	kubernetes image

Install various distributed applications

sealos run labring/helm:v3.8.2 # install helm
sealos run labring/openebs:v1.9.0 # install openebs
sealos run labring/minio-operator:v4.4.16 labring/ingress-nginx:4.1.0 \
   labring/mysql-operator:8.0.23-14.1 labring/redis-operator:3.1.4 # oneliner

Such highly available mysql redis, etc. are all available, so you don't need to care about all dependencies.

Add node

add node :

$ sealos add --nodes 192.168.64.21,192.168.64.19 

add master:

$ sealos add --masters 192.168.64.21,192.168.64.19 

Delete node

delete node :

$ sealos delete --nodes 192.168.64.21,192.168.64.19 

delete master:

$ sealos delete --masters 192.168.64.21,192.168.64.19  

clean up the cluster

$ sealos reset

Build your own ClusterImage

Download helm chart

$ mkdir ingress-nginx && cd ingress-nginx
$ helm repo add ingress-nginx https://kubernetes.github.io/ingress-nginx
$ helm pull ingress-nginx/ingress-nginx

then you can find the download chart：

$ ls
ingress-nginx-4.1.0.tgz

Write Dockerfile

FROM scratch
COPY ../examples .
CMD ["helm install ingress-nginx ingress-nginx-4.1.0.tgz --namespace ingress-nginx --create-namespace"]

OR you can FROM a kubernetes baseimage, sealos will seal kubernetes and ingress into cluster image

FROM kubernetes:v1.25.0
COPY ../examples .
CMD ["helm install ingress-nginx ingress-nginx-4.1.0.tgz --namespace ingress-nginx --create-namespace"]

Build a cluster image

$ sealos build -f Dockerfile -t docker.io/fanux/ingress-nginx:v1.2.0 .

When sealos builds, it will automatically add the image dependencies in the image list to the cluster image,
and save the dependent Docker images in a magical way. And when running in other environments,
it will automatically detect whether there is a Docker image in the cluster.
If there is, it will be downloaded automatically.
If not, it will be downloaded from k8s.gcr.io. Users do not need to modify the docker image address in the helm chart.
The black technology of image caching proxy is used here.

Push to mirror registry

$ sealos login docker.io
$ sealos push docker.io/fanux/ingress-nginx:v1.2.0

run cluster image

$ sealos run docker.io/fanux/ingress-nginx:v1.2.0