Sealos v4.2.0-alpha3 🎉🎉

We are excited to announce the official release of Sealos v4.2.0-alpha3 🎉🎉!

Sealos Cloud: Powerful Cloud Operating System Distribution

Sealos Cloud is a cloud operating system distribution with Kubernetes at its core. Users can directly use Sealos Cloud or run Sealos in their private environment to have the same capabilities as Sealos Cloud. Sealos Cloud offers a range of advantages, including a sleek product experience, fully open-source architecture, consistent public and private cloud experiences, cross-platform compatibility, and highly competitive pricing.

Sealos Cloud Usage Guide

Sealos Cloud offers you exceptional public cloud services for cloud-native applications, making it easy to manage cloud-native applications. Sealos Cloud provides two ways to use: cloud access and private access. The online mode is now officially launched, and offline mode will be introduced in future releases.

Cloud Access

Cloud access is provided by directly accessing the cloud services provided by Sealos Cloud. Just enter the following link in your browser to start using the powerful features of Sealos Cloud immediately:

https://cloud.sealos.io

Cloud access allows you to access and manage your cloud-native applications anytime, anywhere, without any additional configuration and deployment. This makes the online mode an ideal choice for quickly getting started with Sealos Cloud.

Component Introduction

Sealos Cloud's main features are divided into the frontend interface, backend API services, and Kubernetes Operator, working together to provide a complete cloud-native application management experience.

Main Components

• Auth-Service：Provides authentication services using casdoor, ensuring the security and accuracy of user identities.
• Image Hub：Sealos image repository-related services, making it easy for users to manage and use images.
• Desktop：Public cloud frontend service, providing a friendly user interface and operation experience.
• User：User and user group management services, making it easy for administrators to assign and manage user permissions.
• Account & Metering：Provides billing and account capabilities, helping users to reasonably control and plan costs.
• App：Provides the Sealos Cloud desktop application, making it easier for users to use and manage cloud services.
• Infra：Provides basic settings, currently supports AWS and Alibaba Cloud, and may support more cloud service providers in the future.
• Cluster：One-click cluster startup on Sealos Cloud, simplifying the cluster deployment and management process.
• Terminal：Terminal services on Sealos Cloud, providing convenient access and management of cloud services.

For more detailed documentation about Sealos Cloud, please visit https://sealos.io/docs/cloud/Intro.

Sealos Boot: Professional Cloud-Native Application Management Tool

Sealos Boot is the core component of Sealos, mainly responsible for the lifecycle management of clusters, downloading and deploying OCI-compatible distributed applications, and customizing distributed applications.

How to Install

Binary Installation

    curl -sfL  https://raw.githubusercontent.com/labring/sealos/v4.2.0-alpha3/scripts/install.sh \
    | sh -s v4.2.0-alpha3 labring/sealos

Component Introduction

Sealos provides two Docker containers: sealos and lvscare, as well as two binary files: sealctl and image-cri-shim. Below is a brief introduction to these components:

• Sealos Container: This container is the core component of the Sealos project, responsible for deploying and managing Kubernetes clusters and distributed applications. It offers a range of command-line tools to help users quickly build and maintain clusters.
• lvscare Container: This container is used to support load balancing management within Kubernetes clusters. It can monitor node status in real-time, ensuring that the load balancer always routes traffic to available nodes.
• sealctl Binary: This is a command-line tool provided by the Sealos project, used to simplify cluster management tasks such as certificate management, IPVS, hosts, and cluster certificates.
• image-cri-shim Binary: This component is a CRI adapter for the Sealos project, supporting different container runtimes (such as Docker and containerd). It allows Sealos to seamlessly integrate with multiple runtimes, enhancing the project's flexibility and scalability.

Quick Start

# 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 \
    --passwd your-own-ssh-passwd

Changelog

New Features

• 4131325: feat(debt): Debt-controller should delete user resources over 7 days in arrears (#2899) (@xiao-jay)
• 6c0a216: feat: add resource group (#2905) (@xiaohan1202)
• 6ef4df2: feat: grouping subcommands (#2920) (@fengxsong)

Bug fixes

• 5bb06f4: bugfix: the failure to add master after updating the certificate (#2942) (@bxy4543)
• f7bb82c: fix(ci): fix metering e2e install account error (#2901) (@xiao-jay)
• 0c4a3cf: fix: check sg & vswitch existence (#2937) (@xiaohan1202)
• 3de1dc6: fix: fix always return the insecure registry (#2927) (@fengxsong)
• 472d25c: fix: make pre-deploy error (#2904) (@xiao-jay)
• 884f1d9: fix: return image name if oci archive file has names instead of id (#2887) (@fengxsong)
• 09aa95f: fix: rm master taint in single model (#2860) (@mixinkexue)
• ddabe65: fix: use assertion, avoid patching external interface (#2891) (@fengxsong)

Other work

• 89a519b: E2e/apply test workflow (#2952) (@bxy4543)
• 31e4062: Fix login ingress deploy (#2909) (@zzjin)
• 9b7fd80: Move deploy doc. (#2951) (@zzjin)
• cdacf36: Reduce terminal limits a little. (#2915) (@zzjin)
• 5efa4b1: Title: Update auto-release logic to skip deb and rpm packages for non-production releases (#2882) (@cuisongliu)
• 9725ded: add bytebase controller (#2841) (@dinoallo)
• 7ce51bb: add e2e apply test (#2936) (@bxy4543)
• fba6b37: add fetch Kubeadm Config: (#2943) (@bxy4543)
• b2ed4c7: add image-cri-image test (#2849) (@bxy4543)
• 21cdb8b: add local deplopment docs. (#2945) (@lingdie)
• 8a67f56: ci，docs: add account e2e test and docs (#2935) (@xiao-jay)
• 2d8d793: docs(main): Refactor Changelog generation script and update usage guide (#2884) (@cuisongliu)
• 72a58a9: docs(main): add changelog full to shell (#2885) (@cuisongliu)
• 53974f5: docs(main): add debug for merge logger (#2886) (@cuisongliu)
• a100d1a: docs(main): add docs for sealctl (#2922) (@cuisongliu)
• c781a29: docs(main): add docs for user (#2929) (@cuisongliu)
• e5a2041: docs(main): add image-cri-shim docs (#2880) (@cuisongliu)
• de11f2b: docs(main): add robot for sealos (#2959) (@cuisongliu)
• 42e06f9: docs(main): support v1.27 docs (#2939) (@cuisongliu)
• 60b0388: docs(main): support v1.27 k8s (#2938) (@cuisongliu)
• 8c4a998: docs(main): sync code user and email (#2900) (@cuisongliu)
• 18b3447: docs(main): update gorelease config for new release (#2953) (@cuisongliu)
• a929e01: docs(main): upgrade gomod (#2894) (@cuisongliu)
• 696c741: docs: how to write reousrce-controller (#2941) (@xiao-jay)
• e43c77c: docs: translate metering design from CN to EN (#2746) (@xiao-jay)
• b49983d: feat add bytebase application (#2925) (@zjy365)
• c93c368: feature: support checking cluster's no-odd number of master node (#2842) (@pixeldin)
• 9ca8b5e: feature: support pulling multiple images at the same time (#2931) (@dhanusaputra)
• 9256d27: fix len(deleteInstancesByOption.instanceIds) always gt 0 (#2934) (@bxy4543)
• 3018f69: fix multi infra apply (#2960) (@bxy4543)
• 7fd1373: fix notification (#2895) (@zjy365)
• 2fc130b: fix pgsql status null (#2924) (@zjy365)
• a26403f: fix stop kube-apiserver pod cause DeadlineExceeded when update cert. (#2918) (@bxy4543)
• 86e8983: fix sync docs error (#2944) (@xiao-jay)
• be282f8: format(account): format webhook name (#2928) (@xiao-jay)
• 168319f: optimize reset node ip link delete command. (#2947) (@bxy4543)
• 7c66fd2: refactor: add back auto build and auto save abilities in diff command (#2906) (@fengxsong)
• 187be92: refactor: diff command (#2879) (@fengxsong)

Full Changelog: v4.2.0-alpha2...v4.2.0-alpha3

See the CHANGELOG for more details.

Roadmap

In the future development plan, Sealos Boot and Sealos Cloud will continue to expand their capabilities to meet the needs of more users. Our Roadmap includes the following key plans:

1. Sealos Cloud Private Deployment: We will introduce a private deployment solution for Sealos Cloud, allowing users to deploy and run Sealos Cloud in their own data centers or private cloud environments, achieving consistency between public and private cloud experiences.
2. Heterogeneous Deployment Support: Sealos Boot will support the deployment of Kubernetes clusters on various hardware platforms and operating systems, achieving broader compatibility and flexibility.
3. K3s and K0s Integration: We plan to integrate the lightweight Kubernetes distributions K3s and K0s into Sealos Boot, allowing users to choose different Kubernetes distributions for deployment according to their needs.

Please look forward to the launch of these new features. We will continue to work hard to provide users with better services and experiences.

We are very proud to introduce the two major functional modules of Sealos Cloud and Sealos Boot, which we believe will bring more convenience and efficiency to your cloud-native application management. We look forward to your feedback and suggestions so that we can continue to improve and provide better products and services.

Thank you for your support of Sealos🎉🎉.

If you encounter any problems during use, please submit an issue in the GitHub repository , and we will solve your problem as soon as possible.