Sealos is a Kubernetes distribution, a general-purpose Cloud Operating System designed for managing Cloud Native applications.
- Henceforth, envisage all your machinery as an ethereal supercomputer, whose operating system is Sealos, with Kubernetes assuming the role of the OS kernel.
- Rather than IaaS, PaaS, and SaaS, the new paradigm shall solely encompass Cloud OS drivers (CSI, CNI, and CRI implementations), Cloud OS kernel (Kubernetes), and distributed applications.
Utilize the Cloud infrastructure akin to a Desktop computer, with the liberty to install or uninstall any Distributed Application at will:
Some Screen Shots of Sealos Desktop
:
- ☸️ Manage clusters lifecycle
- Quickly install HA Kubernetes clusters.
- Add / remove nodes, Clean the cluster.
- 💻 Download and deploy OCI-compatible distributed applications.
- OpenEBS, MinIO, Ingress, PostgreSQL, MySQL, Redis, etc.
- 🛠️ Customize your own distributed applications.
- Utilizing Dockerfile to build images of distributed applications while preserving all of their dependencies.
- Push images of distributed applications to Docker Hub.
- Integrate various applications to construct a personalized Cloud platform.
- ☁️ Sealos Cloud
- Multi-tenant management.
- Application management.
- Multi-cloud cluster management, deploy Kubernetes and custom applications on any cloud platform.
- Run any distributed applications.
- Cloud terminal.
- App Store.
Installing a highly available Kubernetes cluster with Calico as the container network interface (CNI).
Here, the Cluster images kubernetes:v1.24.0
and calico:v3.24.1
stored in the registry are fully compliant with the OCI standard. However, if you prefer to use flannel, it is also an option.
# Download and install Sealos, which is a binary tool written in Golang. Simply download it and copy it to the bin directory. You can also download it from the release page.
$ wget https://github.com/labring/sealos/releases/download/v4.1.4/sealos_4.1.4_linux_amd64.tar.gz && \
tar -zxvf sealos_4.1.4_linux_amd64.tar.gz sealos && chmod +x sealos && mv sealos /usr/bin
# Create a cluster
$ sealos run labring/kubernetes:v1.25.0 labring/helm:v3.8.2 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]
- Supported Kubernetes versions: 240+ Kubernetes versions Kubernetes with cri-docker runtime
- Other images for distributed applications
Single host
$ sealos run labring/kubernetes:v1.25.0 labring/helm:v3.8.2 labring/calico:v3.24.1 --single
# remove taint
$ kubectl taint nodes --all node-role.kubernetes.io/master:NoSchedule-
Building a custom Cluster image
Reference Building an Example CloudImage.
Storage, Message queue, Database, etc.
Don't be shocked by the following:
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
And now everything is ready.
sealos run labring/kubernetes-docker:v1.20.8-4.1.4 labring/calico:v3.22.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]
- Visit the Sealos website for full documentation and useful links.
- Join our Discord server is to chat with Sealos developers and other Sealos users. This is a good place to learn about Sealos and Kubernetes, ask questions, and share your experiences.
- Tweet at @sealosio on Twitter.
- Create GitHub Issues for bug reports and feature requests.
Sealos maintains a public roadmap. It gives a a high-level view of the main priorities for the project, the maturity of different features and projects, and how to influence the project direction.
Have a look through existing Issues and Pull Requests that you could help with. If you'd like to request a feature or report a bug, please create a GitHub Issue using one of the templates provided.
- Sealos Action
- Bug Verify Example
- Application Image
- Rootfs Image
- Buildah The functionalities of Buildah are extensively utilized in Sealos 4.0 to ensure that cluster images are compatible with OCI standard.