v4.2.1-rc3

Sealos v4.2.1-rc3 🎉🎉

We are excited to announce the official release of Sealos v4.2.1-rc3 🎉🎉!

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.1-rc3/scripts/install.sh \
    | sh -s v4.2.1-rc3 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

What's Changed

• docs: Automated Changelog Update for v4.2.1-rc1 by @sealos-release-rebot in #3043
• add docs how-to-deploy-postgresql-with-kubeblocks-on-sealos-cloud by @sakcer in #3045
• docs(main): changelog body support by @cuisongliu in #3044
• Fix readme md usage. by @zzjin in #3046
• refactor(main): add operator interface by @cuisongliu in #3048
• docs(main): remove registry to sealos Experimental by @cuisongliu in #3047
• fix: compress/uncompress offline images by @fengxsong in #2966
• add app providers logo by @zjy365 in #3054
• feat: logs analyses by @c121914yu in #3041
• fix: running in container as user root by @fengxsong in #3056
• CI: add create dev cluster image ci by @lingdie in #3058
• rename CopyR to Fetch by @fengxsong in #3061
• CI: Switch build dev to release by @lingdie in #3062
• fix cluster image by @lingdie in #3064
• refactor(main): trigger release ci by @cuisongliu in #3063
• CI: fix image build ci. by @lingdie in #3065
• fix image name by @lingdie in #3066
• perf: export yaml name;focus restart app; by @c121914yu in #3067
• refactor(main): add image replace status interface by @cuisongliu in #3060
• fix: invalid reference format by @fengxsong in #3070
• fix ingress's backend error by @lingdie in #3071
• Fix demo usage of side-login ingress. by @zzjin in #3072
• refactor：smooth and simple new desktop by @zjy365 in #3059
• feat: desktop pwa by @zjy365 in #3077
• add client id and secret in auth svc by @lingdie in #3078
• fix app cr name. by @lingdie in #3080
• Update image by @lingdie in #3081
• refactor(main): add bot for link check by @cuisongliu in #3083
• feat. init cloud cluster image by @lingdie in #3082
• fix role binding by @lingdie in #3088
• feat. fix cloud cluster image by @cuisongliu in #3087
• feat. fix cloud cluster image (#3087) by @cuisongliu in #3089
• refactor(main): add bot for link check by @cuisongliu in #3085
• refactor(main): enable build flags isolation by @cuisongliu in #3086
• fix terminal and applaunchpad deploy yaml by @lingdie in #3091
• feat: cmd and params input way by @c121914yu in #3074
• perf: default domain by @c121914yu in #3092
• fix deploy file by @lingdie in #3093
• feat: env set secretName by @c121914yu in #3095
• fix app launchpad env by @lingdie in #3099
• fix: auto-completion of arch role and default SSH initialization in single-node mode by @LZiHaN in #3102
• Refactor preprocessor by @fengxsong in #3101
• docs(main): update latest sealos version by @cuisongliu in #3104
• feat: terminal add loading animation by @zjy365 in #3097
• fix: modify the desktop height acquisition method by @zjy365 in #3096
• fix: desktop image style by @zjy365 in #3105
• docs(main): change issue token by @cuisongliu in #3106
• Fix bytebase nginx controller. by @zzjin in #3111
• add cert prepare readme by @lingdie in #3100
• refactor: rename interface and function names by @fengxsong in #3112
• Try add db/bytebase controller ci. by @zzjin in #3115
• Fix bytebase Dockerfile to support outside binary. by @zzjin in #3116
• Dev module by @zzjin in #3117
• Update pr,support auto copilot:all. by @zzjin in #3118
• Init adminer controller. by @zzjin in #3107
• refactor(main): replace registry password config generator by @cuisongliu in #3119
• Dev adminer by @zzjin in #3120
• refactor(main): change config to envs by @cuisongliu in #3121
• move registry save command to sealctl by @fengxsong in #3122
• Dev adminer by @zzjin in #3123
• refactor(main): add registry docs and fix registry save bug by @cuisongliu in #3124
• feat: resources monitor, metering controller, billing controller, billingrecordquery, pricequery controller by @bxy4543 in #3008
• fix ci error by @bxy4543 in #3128
• Add type status hide/show system app. by @zzjin in #3127
• feat: add withcontext functions in ssh interface by @fengxsong in #3129
• Move apps.displayType to spec. by @zzjin in #3133
• update release error by @cuisongliu in #3132

New Contributors

• @sakcer made their first contribution in #3045

Full Changelog: v4.2.1-rc1...v4.2.1-rc3

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.