Welcome to the v4.3.1-rc1 release of Sealos!🎉🎉!

Changelog

New Features

• f7d140bf09aa7c32c421f69b308a328fc83694d6: feat: add and delete master or worker nodes with different ssh settings (#3525) (#3571) (@sealos-ci-robot)

Bug fixes

• a40ff9177059aa47811cab5f15f1c8698a37ca0e: fix: check hostname unique in creating new cluster (#3569) (#3570) (@sealos-ci-robot)
• bbf88d0419ec3fff3e3a1f87bd78a5d34b3ed916: fix: if the root user is not specified,sudo should be disabled. (#3598) (#3599) (@sealos-ci-robot)
• aed2a4623f574201cf78d67c0acbcf4f33b2b01d: fix: upgrade cluster (#3588) (#3590) (@sealos-ci-robot)

Other work

• 2ef981b614dacb363671be197f564c455f251945: feature(v4.3): delete workflow auto build controllers (#3557) (@cuisongliu)
• b68c4b8170d2ee29c36c820d69617a14841dd706: feature(v4.3): delete workflow link check (#3558) (@cuisongliu)
• 8ae61fb94656eb376d950917fc15302f095ccc13: feature(v4.3): default support tmp registry build image (#3535) (#3536) (@cuisongliu)
• 0a45544e190ecedebc6271718403c004394e71e0: fix cluster status (#3572) (#3574) (@sealos-ci-robot)
• 6c156c7ea2dc593b10582a87a90b79f2089eccca: fix e2e apply test with infra && fix wrong ssh.fetch interface method implementation (#3560) (#3567) (@sealos-ci-robot)
• 65b7a43da4fbe3103fe02db0780bfb3491ecc1dc: fix the current cluster does not exist, but the creationTimestamp of the expected cluster is not zero. (#3549) (@bxy4543)
• 98719a4e3ed6c9fc4e2b3a017aa2fc670ffc451a: refactor: remove versionutils (#3592) (#3593) (@sealos-ci-robot)

Full Changelog: https://github.com/labring/sealos/compare/v4.3.0...v4.3.1-rc1

See the CHANGELOG for more details.

Your patronage towards Sealos is greatly appreciated 🎉🎉.

If you encounter any problems during its usage, please create an issue in the GitHub repository, we're committed to resolving your problem as soon as possible.

Welcome to the v4.3.0 release of Sealos!🎉🎉!

Changelog

New Features

• aaafe9a49853b596536c8c1de10e1d682cc3ceed: feat: support dual-stack (#3509) (@ghostloda)

Build process updates

• f3415f4403880cef422a20913fa41fae09d93a36: build(main): add ci for latest (#3513) (@cuisongliu)
• 7ee53f1d67d62018b301cd11e4097bc4cb34b298: build(main): add ci for latest (#3516) (@cuisongliu)

Other work

• 9259b2d21bf6507d9ced75a15e47b0742b72c28c: feature(main): add commitor for release (#3487) (@cuisongliu)
• 3a07652bcf09c002a449018fbdc5147d18e31993: refactor: cri_server multiple versions of AuthConfig (#3507) (@muicoder)

Full Changelog: https://github.com/labring/sealos/compare/v4.3.0-rc1...v4.3.0

See the CHANGELOG for more details.

Your patronage towards Sealos is greatly appreciated 🎉🎉.

If you encounter any problems during its usage, please create an issue in the GitHub repository, we're committed to resolving your problem as soon as possible.

Welcome to the v4.3.0-rc1 release of Sealos!🎉🎉!

Changelog

New Features

• 0a6ea4f44d87d42a80e9771218aff77bd5bb5b34: feat: add host ssh and sftp client map cache for sftp (#3450) (@ArenaSu)

Bug fixes

• 75231c231766f620c7293155a2e67ddd37cde0d7: fix(main): fix merge support $() (#3427) (@cuisongliu)
• 9da41c56873f1342d05e2053b03afe9113af9fc8: fix: upgrade k8s version failed on non default ssh port (issue #3069) (#3434) (@yangxggo)

Other work

• 472c7b50b31062dcfb4aad89cafcd2baea7d2149: Feature:sudo support for scp (#3421) (@ghostloda)
• 0567195db44fd25469094fbe90a90b0a7973b125: refactor(main): auto cherry pick (#3412) (@cuisongliu)
• 81cd5f7023e598e4dc19306a1a594c5117b46964: refactor(main): delete node for check (#3405) (@cuisongliu)
• 933bc8a6589164f9bc25e9d2909bd76031c3fa6a: refactor: save and load subcommand support multiple images in a single tar… (#3442) (@fengxsong)
• 27ea418989bb99cbbc1f52d5a312a68d99c60617: support old version of kubelet-config (#3447) (@yangxggo)

Full Changelog: https://github.com/labring/sealos/compare/v4.2.3...v4.3.0-rc1

See the CHANGELOG for more details.

Your patronage towards Sealos is greatly appreciated 🎉🎉.

If you encounter any problems during its usage, please create an issue in the GitHub repository, we're committed to resolving your problem as soon as possible.

Welcome to the v4.2.3 release of Sealos!🎉🎉!

Changelog

New Features

• 77e312e408053e483c4b17e40dd12c6cf1115f8f: feat: support override platform in diff command (#3376) (@fengxsong)

Bug fixes

• 450b52aa90a0193cf49898b76d50c09dc89a578a: fix: error while unmount container mountpoint (#3385) (@fengxsong)

Build process updates

• 4e0e84b2a7af0a35e6d9a6dcbeeae4477055c761: build(main): add sync patch image (#3398) (@cuisongliu)
• 0ce9c15ef92c6ae820f1f4a3b43ad0499e318ebc: build(main): auto renew issue and auto comment body (#3393) (@cuisongliu)

Other work

• 7413c81f125fb16e99c44925c41d76857d51ef3d: docs(main): upgrade version for kubeadm (#3371) (@cuisongliu)
• 2b42496c3c0afb766d8d55a3fd98177b4b155bca: restore easter egg feature in diff command (#3388) (@fengxsong)

Full Changelog: https://github.com/labring/sealos/compare/v4.2.2...v4.2.3

See the CHANGELOG for more details.

Your patronage towards Sealos is greatly appreciated 🎉🎉.

If you encounter any problems during its usage, please create an issue in the GitHub repository, we're committed to resolving your problem as soon as possible.

Welcome to the v4.2.2 release of Sealos!🎉🎉!

Changelog

Other work

• 492e9091e840efcddb91290be80995511ac2cecd: revert: rollback mergo version (#3364) (@fengxsong)

Full Changelog: https://github.com/labring/sealos/compare/v4.2.1...v4.2.2

See the CHANGELOG for more details.

Your patronage towards Sealos is greatly appreciated 🎉🎉.

If you encounter any problems during its usage, please create an issue in the GitHub repository, we're committed to resolving your problem as soon as possible.

Welcome to the v5.0.0-alpha1 release of Sealos!🎉🎉!

Changelog

Other work

• c0cc8e78f3e52fb4ae4d5e8fd04147fff0c8cfb5: 🤖 add release changelog using rebot. (#3352) (@sealos-release-rebot)

Full Changelog: https://github.com/labring/sealos/compare/v4.2.1...v5.0.0-alpha1

See the CHANGELOG for more details.

Your patronage towards Sealos is greatly appreciated 🎉🎉.

If you encounter any problems during its usage, please create an issue in the GitHub repository, we're committed to resolving your problem as soon as possible.

Welcome to the v4.2.1 release of Sealos!🎉🎉!

Changelog

New Features

• 03e43356c73c5ef07b8e0fc3e6d50fe62ef25fdb: feat: desktop communication app change i18n (#3324) (@zjy365)
• 0a45fe75ecfe5bed0ac1ea74c4261e63fd2db173: feat: js-cookie (#3322) (@zjy365)
• 2de6e52812e87b02b0a65ef012e316f3324992f4: feat: support override platform flags for inspect command (#3304) (@fengxsong)
• 0866fbbe051ee06c8fdf6fa0452878cc520c2706: feat:costcenter (#3326) (@xudaotutou)

Bug fixes

• 2114a8744b5b262928563ec7a246e838f06dade3: bugfix: fix the wrong unit (#3313) (@nowinkeyy)
• dfa71f933e986473da3461cb8fe8e116fe6e4273: fix: avoid fetching local repos repeatly (#3336) (@fengxsong)
• bc26a4ae7b525c1460f44e3c15f2b127988dee62: fix: i18n and db opsrequest (#3348) (@c121914yu)
• aa9be9451d6f17f53632e4482c47a7b3c618548e: fix: launchapad i18n & update app way (#3321) (@c121914yu)
• 2a0e3e867df8756ff80f6c1ae57538333abf3c70: fix: launchpad i18n init;fix: do not split command (#3329) (@c121914yu)
• 502bee1437d919cbf64b974556cac2fc17990a76: fix: modify cookie policy (#3325) (@zjy365)
• 5eeb554e5b510abedfa168612327b86a2319c2d0: fix: retry when error contains internal server error message (#3347) (@fengxsong)
• 807a736100fba5b20efa7970237d099afec47e0a: fix:fix version comparison issue (#3328) (@overstarry)

Other work

• a4c62adf98682970049ab98a5ee26719e0f427ca: Add adminer prints. (#3346) (@zzjin)
• e2514f060e60d3dddd1a87dd84f413847b1121ce: Fix desktop login error (#3320) (@xudaotutou)
• 0118f9fe56c6268d6ec2a90fdd0106dd24c27f76: SDK enhances communication, app supports event monitoring (#3311) (@zjy365)
• 261d85cc8cfd465a3cad7b252bef01a772a94ee2: Try using probe to check pod ready. (#3345) (@zzjin)
• fb191f4fbfb97b9692ecfb9b0e150d61dc249704: Update README (#3341) (@yangchuansheng)
• ae21df79204adeecde7eaf913cf8237628d5bd58: Update format linter. (#3317) (@zzjin)
• 8e1ead6a1ea1b3476980401f59bf7a147c628379: Update reflector namespaces. (#3351) (@zzjin)
• 29e86d2971dc4559ca6ad30f207f7600c1985d9d: debt controller implement (#3160) (@bxy4543)
• ff8d2dd74395ee278727df120642d3b03f5c11f4: docs(main): fix link for docs (#3309) (@cuisongliu)
• 475a87bb8d2d047cd387c32f64a687d92b24dd55: docs(main): fix link for docs (#3310) (@cuisongliu)
• 7eae15a8bbdfd03e421b36e9adae99da6718acbb: fix resources controller Kubefile (#3332) (@bxy4543)
• 7185ae7057e62027edbb5c5dc29d8c44caca85b8: fix resources controller Kubefile (#3333) (@bxy4543)
• fe6da0a030e6883f3b4447a66ca771cf8bf4309a: fix(cert sign): not get the correct first svc ip from cidr (#3308) (@yldian)
• 46f3003b8dd21310fab7008be43ef2046ab05655: fix(fronted desktop): Cookies are not set by default (#3301) (@xudaotutou)
• b2bba64c0b3a780b76651fda2721ed44a40ebe58: fix(frontend/costcenter): fix i18n (#3330) (@xudaotutou)
• b0a0461b6cba7215fce272a7eb24b5437c7df242: fix(frontend/costcenter):fix i18n (#3335) (@xudaotutou)
• 86e80ed3690bccee81def11e8a5dd313f3721b05: improve cloud deploy (#3339) (@lingdie)
• 49e9981cdf7410e1e2fa6c36292d249315ee9a57: realize timing monitor resources;add mointor, metering to automatically build container image & cluster-image. (#3240) (@bxy4543)
• 4fda7eaec6e19e8d718f79473218765c5d48baf1: refactor(main): add ednpoint check for adminer (#3300) (@cuisongliu)
• 4e1f1f79fdd29ed2ae83f15a96d7afa1eb4bbfd9: refactor(main): add ednpoint rbac (#3303) (@cuisongliu)
• 456b0991df4044acefe11085c4beba5da1e85b60: refactor(main): add link and report (#3306) (@cuisongliu)
• 837234467679471f730bbe38cdc9e74a939898d8: refactor(main): add pull_request_target for checkout (#3314) (@cuisongliu)
• 9101369cd8b00a115cfa53fd034ce8714c5e1a59: refactor(main): add qa for loggers (#3307) (@cuisongliu)
• 18820d0f6d0b963a3eddb9ed8801f68645ef9ad5: refactor(main): fix ci code error (#3323) (@cuisongliu)
• b6d1417ac0ede86eeb8f112a724384bcc68d7982: refactor(main): update link pr action (#3315) (@cuisongliu)
• 33c69299e7e50f567258f1586c0c9f50e7a495f6: refactor(main): update registry when node is update error (#3312) (@cuisongliu)
• daf455b9dda41f610969d18ac7c4b65628eea64a: refactor: registry command with exampleprefix var explicitly (#3305) (@fengxsong)
• e11903e6bc8ed6937e2e91b664a80346504c92e8: update app crd (#3340) (@lingdie)
• 43d8190ef911b345d35052db840ba3d3cd14690c: update issue num (#3343) (@lingdie)
• 8f868d53a9222ea5e0ab488fd0f6f9f2310c03f6: 🤖 add release changelog using rebot. (#3299) (@sealos-release-rebot)

Full Changelog: https://github.com/labring/sealos/compare/v4.2.1-rc6...v4.2.1

See the CHANGELOG for more details.

Your patronage towards Sealos is greatly appreciated 🎉🎉.

If you encounter any problems during its usage, please create an issue in the GitHub repository, we're committed to resolving your problem as soon as possible.

Welcome to the v4.2.1-rc6 release of Sealos!🎉🎉!

Changelog

New Features

• b567669d5cc49681c75730901062b28baba9e51a: feat(desktop):login (#3276) (@xudaotutou)
• 134904e55a7b80f2c8eb41574fee3dcf88ee524b: feat: app launchpad i18n (#3235) (@zjy365)
• 0d9ea570595efa7456cc5b5dd05e1125ccce1538: feat: apply limitrange;perf: db min cpu and memory;docs (#3234) (@c121914yu)
• 32572c676bad95f1e29337111b8f66eac24b0924: feat: desktop i18n (#3221) (@zjy365)
• b08fc64e0a0a44359202179dd09c5cdec8d2b099: feat: remove the i18n language prefix (#3274) (@zjy365)
• 49dd20305843b4ecfa40925470b9eeeb6343ce6b: feat: terminal connection stability (#3263) (@zjy365)

Bug fixes

• 1029bfd50fb7efd93eddd86d0027bf08655d0b4e: fix: add default configs in storage.options.overlay section (#3236) (@fengxsong)
• f4382af21e13b93dd5c47c0c551b64f74eb9b446: fix: name regx (#3254) (@c121914yu)
• f9b4da648b336c375c641a0146d535fe4f9d9b00: fix: return early to avoid calling imagesaver (#3288) (@fengxsong)
• f150ecb9001a1ec587508e6510a64b3b654e052f: fix: router back invalid; perf: database ux (#3241) (@c121914yu)
• 469d6f7c4b9a4799a9b5dfc9da4508610f23dc1d: fix: set default storage config path for root users (#3293) (@fengxsong)

Other work

• be23cefe06af6c36bbbab3c4e4b2540758759d79: Add ARCH doc. (#3262) (@zzjin)
• a7a1765730ffd0ac808e70750ab290f4651e2317: Add adminer status Check to adminer. (#3295) (@zzjin)
• 0508e4da612aefa3f3562f655cecec9e399f9444: Added an example of how to connect to the database in the WordPress (#3270) (@ElonMuskkkkkk)
• 253cd3200bf7c0dd11f881cd6fbbf5d72765ddcc: Adjust documentation example structure (#3261) (@bxy4543)
• 053fb5eb47cf73e5d8b50e6380c6ab0db7c52f4e: Delete database-launch.png (@sakcer)
• 146b329ad8773fa7e5870761ce453f61e74ba99f: Fix adminer connect driver name. (#3230) (@zzjin)
• 1544a8955647f992063cd1f160151838174d11a2: Fix ass go-lint-ci version. (#3244) (@zzjin)
• 16cdabf7889283613eb38ed9f4b33acd8fd9236e: Fix back (#3253) (@zzjin)
• 484275079b5f542d70c612b3e858ddaea97d8a79: Fix life-circle sidebar (#3290) (@zzjin)
• 7bbba06f54b3e18da48685b3c7b73054a02fc2ca: Remove files with no more needed. (#3285) (@zzjin)
• 99e6accf65e9e6564b7ee04813c72aadf6277cb8: Revoke lint version 1.53 bug. (#3242) (@zzjin)
• ce700f48b40faa9bc6eec2f8470a3d7e505d8890: Update aap cr, support i18n. (#3243) (@zzjin)
• 522aefa768639aa9ca5d6534225a5bab8bee26af: Update doc links. (#3284) (@zzjin)
• 53c788e852ace030b85f260a5b2b4c9efef2d7d2: Update install-db-with-database.md (@sakcer)
• 77ffa22b3f16a65708c4f504507db87c0d582e01: Update install-db-with-database.md (@sakcer)
• 159cd00ef3787dbf4c7de6f8664b3390ce69bbe8: Update install-db-with-database.md (@sakcer)
• d1051809083aed3d25e40d0a3c366e699ac6c13c: add doc install-db-with-database (#3239) (@sakcer)
• ee3c5c651510d9f1f9e120b24eb9909d424efd2a: add some examples in README (#3281) (@fanux)
• ca49ff88ce59a4bec3cb7c356ae71dbc60f074ed: change database-launch to chinese version (@sakcer)
• 1b68ca80b652d4de6011550d488f558053689963: delete how-to-deploy-postgresql-with-kubeblocks-on-sealos-cloud.md (#3282) (@sakcer)
• e8f3d01afb8cb052f859fcc810ace2a4ad31e502: delete the old version of markdown about database (#3249) (@ElonMuskkkkkk)
• 3980d37399a15c977104c525a48ad3e2bb634f98: docs (#3255) (@c121914yu)
• 6c5fb2bcbbf2e711008bd0c6644b890c020b8a47: docs(main): fix lifecyle-management from intro (#3256) (@cuisongliu)
• 163bcfcce2dc9d9a04ce9d8777bbbaf69f305d0f: docs(main): add docs issue template (#3278) (@cuisongliu)
• 1f42cdbf24abf0a1496602c5fb0a5cdb330b0f8f: docs(main): add tips for sealos buildah rm (#3291) (@cuisongliu)
• 0c8d89aa6646d0fe404ec41ede611f5de7a31c93: docs: Add Desktop image for Intro documentation (#3252) (@yangchuansheng)
• 73b168edb57cc82199645ea240e83106c351b2cb: docs: Add terminal documentation and images for platform components (#3265) (@yangchuansheng)
• 56f2e39cbffc625c20f7f66bbcbd0f218f988352: docs: Update App Launchpad quick start guide (#3248) (@yangchuansheng)
• d73fcb1c550076e87858ffe950c169e9f2a5e3f3: docs: Update README (#3246) (@yangchuansheng)
• 6090210673f3330b54db88b3178911f0ad3cdf02: docs: fix part of the link failure (#3267) (@nowinkeyy)
• 019d321b26024138476eeb59e6579d95af26a46d: docs: fix part of the link failure (#3271) (@nowinkeyy)
• ce99fdfd72fde6f8ef5805e21eeac7013487dd18: docs: modifying docs format (#3268) (@BanTanger)
• 0e21d6085cdc993703cf8b948e3690cc8376a2d6: feature(main): add buildah labeler (#3289) (@cuisongliu)
• 9feb721d17bc79c7f9f276fefc5ff9b6c3e2e46e: feature(main): add docs for sealos run (#3292) (@cuisongliu)
• 6b228fe9d64946b83f3b70ed890919c02a471ca1: feature: recharge extra gift amount (#3296) (@nowinkeyy)
• 5a536fe5a17f8a4197492b90f3e06fe3e187b5ff: fix docs img link (#3286) (@bxy4543)
• 62e25cb1e5f0ad1f7c7e3189cb36aad4747bf19d: fix readme (#3297) (@bxy4543)
• fa97893c8f9b7fc8c2d0dab9c6bb15a6be11e34d: new app: DB Provider (#3232) (@c121914yu)
• 534a5924b6d18ef6a5f906a58f002f40ac3466d3: refactor(main): add docs for registry sync solution (#3226) (@cuisongliu)
• 8e4dd4a906edebddaf7057755b5f02645b6592a5: refactor(main): add docs for lvscare (#3233) (@cuisongliu)
• d029b711fb6cf6e56da0e5cad9f7bef524a8cef7: refactor(main): add labeler for ci (#3259) (@cuisongliu)
• 78b250996dbe78b10945fdee24d58b0a1e3e8f94: refactor(main): add master to qa (#3283) (@cuisongliu)
• 2e144779753500c3cf3e31bfc9df9eabacfd43dc: refactor(main): add qa for docs (#3250) (@cuisongliu)
• a4661fe54b023088a51328c53e7609eded8e453c: refactor(main): add qa for main docs (#3223) (@cuisongliu)
• f4049753559f4f6f32996539d9fbd4649d759860: refactor(main): add skip error for sync (#3238) (@cuisongliu)
• bfe872050dcc4b842a97df896e7ca1771e64f828: refactor(main): add translator for ci (#3264) (@cuisongliu)
• ef61e0952f1654caa82976d19983f450b0c8537d: refactor(main): release docs (@cuisongliu)
• a5b21e22b9dea74fa18f10652a90933e959e04ee: 🤖 add release changelog using rebot. (#3229) (@sealos-release-rebot)

Full Changelog: https://github.com/labring/sealos/compare/v4.2.1-rc5...v4.2.1-rc6

See the CHANGELOG for more details.

Your patronage towards Sealos is greatly appreciated 🎉🎉.

If you encounter any problems during its usage, please create an issue in the GitHub repository, we're committed to resolving your problem as soon as possible.

Sealos v4.2.1-rc5 🎉🎉

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

Sealos : A Cloud Operating System designed for managing cloud-native applications

Sealos is a cloud operating system distribution based on the Kubernetes kernel. It adopts a cloud-native approach, discarding traditional cloud computing architecture, and shifting towards a new architecture with Kubernetes as the cloud kernel. This allows enterprises to use the cloud as effortlessly as they would use a personal computer.

Deploy your app on Sealos

Try online demo

Core features

✅ Instant Kubernetes Usage Upon Login: There is no need to install a Kubernetes cluster. Sealos provides the ability for multiple tenants to share a Kubernetes on the public internet. It also offers strong isolation capabilities to ensure the data safety of each tenant.

✅ Swiftly deploy any application on Sealos: With the in-built App Launchpad, effortlessly deploy any application in an astonishingly short span of time.

✅ Resource Saving and Cost Reduction: You only pay for the container. The automatic scaling function fundamentally solves the problem of resource wastage, saving between 10% to 40% in costs.

✅ Easy Public Network Access: Sealos automatically assigns a secondary domain name to your business, helping you achieve easy public network access. It also supports custom domain name binding.

✅ Efficient Database Service: Sealos offers a service that allows businesses to create high-availability databases within seconds. Through service discovery, the internal network DNS can connect directly to the database.

✅ User-Friendly Operating Experience: Sealos has an in-built terminal that supports command-line operation of the Kubernetes cluster, and also has in-built App Launchpad, allowing you to have a good user experience on Sealos, regardless of your familiarity with cloud-native technology.

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

Changelog

Other work

• 5138733c3bc2d816873e50eccfc3a1feed6741db: refactor(main): fix release notes (#3224) (@cuisongliu)
• 65129e0b8128381dc6daec75042305a30bb16f06: 🤖 add release changelog using rebot. (#3227) (@sealos-release-rebot)

Full Changelog: https://github.com/labring/sealos/compare/v4.2.1-rc4...v4.2.1-rc5

See the CHANGELOG for more details.

We are very proud to introduce the functional modules of Sealos , 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.

Sealos v4.2.1-rc4 🎉🎉

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

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

• ff4ef1b86cf6dbde55aee3d972758902ac33d29e: feat: add max limit in podline chart (#3140) (@moonrailgun)
• 6f913384a9d856a58ad2e910a95a2daf3daa4a82: feat: add more verbose output while syncing registry (#3181) (@fengxsong)
• 1b97f79ccbb2daf5a35c587e86efb877bf064c67: feat: add registry sync command (#3173) (@fengxsong)
• be1f9864f23532c9e6b694d85c52c8e27227890f: feat: make manifest command visible (#3159) (@fengxsong)
• 138521704d508d793e58be0b36aae621de975148: feat: more apps and hover ball (#3126) (@zjy365)

Bug fixes

• 96145f888cfbefb08218692847a364e1764126da: fix: can't find variable structuredClone in safari (#3158) (@zjy365)
• f8a17787822714c5fdf21f2a75cc86fadb88adfa: fix: commandline usage output (#3219) (@fengxsong)
• c3744ed64658b7020e531d839f6f81f7874cc2f6: fix: correct descriptions of env settings (#3164) (@fengxsong)
• 2a7380b370f7c1d234ff15b729eb0f8f4714dae0: fix: fix loop call which occur in throw error in onmessage callback (#3150) (@moonrailgun)
• 7ab33208c638b0f062f9b677ce82718cf66d72e3: fix: if a command requires buildah module, call SetRequireBuildahAnnotation explicitly (#3146) (@fengxsong)
• 7bcc3bca5632794a8bec4953a12f6c536c0cfa0a: fix: name of BUILDAH_FORMAT env key (#3145) (@fengxsong)
• c34fbee89d637d2e2aec36fa1f92f0d595551249: fix: window bug & notification field & modify terminal color (#3147) (@zjy365)

Other work

• 4d33254a1403af2ff4e8f10c0700798b0d05a640: Added Hyperlink for twitter in README.md (#3153) (@Harshad112)
• a4e9c1c79139ed0ffb2eba4141a7621598267b3b: Added documentation for quickly deploying a database and wordpress with sealos (#3178) (@ElonMuskkkkkk)
• 07a7f70a408861b3b51efafbe6446f491756b280: Added documentation for quickly deploying a database and wordpress with sealos (#3194) (@ElonMuskkkkkk)
• 58858354d566d81a852639ce689a2a5f51bcf33d: Auto translate Intro.md (#3180) (@zzjin)
• cbfaea21f2dac9251a7708df8ca58a8f3a5c727e: Fix missing intro endpoint. (#3171) (@zzjin)
• 491dd2f48b0a46321cfc8c990eba613fdcef93d0: Fix typo. (#3185) (@zzjin)
• da8afb066e0365b37657d57ebc490be4a9f70e70: Frontend perf (#3225) (@c121914yu)
• 0b86ceb5f84e11c7ee6de2f8805705bdd5207e5f: Manual change position (#3212) (@zzjin)
• 27d6abbc26c7a50aa8e80a06271e2978d5f9413a: Minor updates: (#3148) (@zzjin)
• aa14645b4cfa28ef0ce7f99edc8e0c566d0ce496: Move doc sidebar config into main repo. (#3184) (@zzjin)
• 606bc14acf31b9acedbcd38e1d8280890804763b: Optimize the title (#3214) (@nowinkeyy)
• 71318a4c0a4eca71536458eb2dedf4343f6114ff: Refactor docs dir. (#3170) (@zzjin)
• 1f7ecfe1c62a66d34abcad2ff90c8c17ccaa238e: Restructure the directory structure (#3203) (@ElonMuskkkkkk)
• bd16b9e1b2a5b5e691731ddfd1183c0a77392662: Restructure the directory structure (#3207) (@ElonMuskkkkkk)
• f9ab4172dd345bfd5a8449d0afdab4f8813d9d84: Restructure the directory structure (#3210) (@ElonMuskkkkkk)
• 55bbb66efc1fcde7db0611ce2dec7e69c6ef602d: Update Intro.md (#3142) (@Yvan-code)
• 9d03c72600935fe3cb3cc5a8a4f13e4671e88c5a: Update Intro.md (#3179) (@yangchuansheng)
• 6ebe11b92f221ace41054b0ff79215ece4105c22: Update adminer provider. (#3162) (@zzjin)
• 655196af17c7f87f99e8bb160c9d133bcdb82847: Update app cr displayType (#3152) (@zzjin)
• 96d24582212705d25ed5fa00e17fa51512d82ff7: Update docs, remove docs/4.0/apis. (#3163) (@zzjin)
• 0007374f776b70ce02b3279d3b72a10e14ccb8d7: Update icon&fix apply (#3135) (@zzjin)
• 8242d6c808ae970b37750d9afbe9eb6f0f59f4b5: Update sidebar position. (#3215) (@zzjin)
• 3800df71c14c6cd4f55b82829d69171c5b468ce5: [ImgBot] Optimize images (#3200) (@imgbot[bot])
• b71600e300cdfb446526c5775828f14bcc286bed: add additional exemplars: halo && uptime kuma (#3174) (@bxy4543)
• 21d6af7afd3892bfcdf835e8100d8a85ebf83665: add docs for bytebase in both en_US and zh_Hans (#3172) (@dinoallo)
• 5d787233b9a97d98112236b230d9db3cdc3dd1b2: add low-code-platform (#3211) (@nowinkeyy)
• 8299dfcefdde2a6b327f6fa19d2119fb4e3e37c1: correct the title (#3217) (@nowinkeyy)
• 8226a823298dba1250704b7b98ab149a2cc271a5: docs(main): add registry sync docs for build (#3222) (@cuisongliu)
• 576679db8b2bd244e086ea07612d49315fff2248: docs: Add Chinese (Simplified) quick-start documentation with new images and instructions. (#3182) (@yangchuansheng)
• 722acdbafd81fbb0400c24649c924b8d1ac1624d: docs: Add Kubernetes deployment tutorial with terminal (#3198) (@yangchuansheng)
• a204b3ec1450ac60c0bc2bf8495083302d7fa31c: docs: Add new images and update file names in quick-start guide. (#3193) (@yangchuansheng)
• ddab1c56aeb2a86f0dd9f5643f887d46e32f9dcd: docs: Improve Sealos introduction (#3189) (@yangchuansheng)
• 4fb261f3f7faa58f9fda4276bbe405782dae6c18: docs: Refactor YAML conventions and code block language specifiers (#3199) (@yangchuansheng)
• 72ab0eb92554c7dd7365d8e8f2cd683cdcc939bb: docs: Remove docs/4.0/docs/quick-start/index.md file (#3197) (@yangchuansheng)
• e4da55fdbe63238c4af9487ffa2d869509f7623d: docs: Remove deprecated features and unused images from README and docs directory. (#3218) (@yangchuansheng)
• 7027fb1a50e085746d9dc1f39a586948f0673f66: docs: add examples pageplug.md (#3176) (@nowinkeyy)
• 49e641decc70bc6b4bddcbaf030ced40ab323671: docs: applaunchpad dbprovider install-fastgpt (#3195) (@c121914yu)
• f943178149517e5a9f42135c04531d4701f05a02: docs: cp docs (#3208) (@c121914yu)
• cb58670e97ad2f204f590a0c41595bf9f3180b90: make bytebase request less resource (#3157) (@dinoallo)
• 833a6affe9bc7ebd18a0f9ab274786752f19580a: mv docs and pics path (#3206) (@nowinkeyy)
• ca838639dd05d684043b296bc66fd647612f1f28: mv docs image path (#3204) (@bxy4543)
• 1aaa0700b1b20c2c3d2f72e875d4a764c8890d4b: mv pics path (#3209) (@nowinkeyy)
• 28f6e5493118cd02c6e73febbc85a63bd002c9a5: optimize docs (#3190) (@bxy4543)
• 43e7e2e058bc55fe029b3c3639743ad836851b4c: optimize the title (#3213) (@nowinkeyy)
• aab8beffe2a8f6b2156af6a8e696638e523aac90: perf: compress default desktop background size. (#3149) (@moonrailgun)
• b37ad2c269dd5aa29f00858a47169e0902becc29: refactor(main): add lifecycle mardown (#3188) (@cuisongliu)
• 5d27f955d8405031df11d2e3a100b65b80de5bdf: refactor(main): add lifecycle mardown (#3177) (@cuisongliu)
• 88dfd8f91de0e33de1648204d0d73520182e92fa: refactor(main): add lifecycle mardown (#3202) (@cuisongliu)
• 6cc595e830b932566c9cbe35687654526c18bea6: refactor(main): add lifecycle mardown for cri-image-shim docs (#3183) (@cuisongliu)
• ed93ee16ce7b05fe94fd732d26b33effbc0e46f6: refactor(main): fix ci error (#3139) (@cuisongliu)
• 66271244a1eaaf3977412ab10b2f4cfed1c22d1c: refactor(main): remove registry compression (#3166) (@cuisongliu)
• 22289636a79c266ec44e211230084e7a35c75017: refactor(main): using registry mode build save images (#3154) (@cuisongliu)
• efb36bd1ec51a1e723952bc24b244dfc8f6260e4: refactor: add sync mode impl (#3113) (@fengxsong)
• 3818b78064358c83200d17ead2492f47a649dff3: revert: remove easter eggs in diff command (#3186) (@fengxsong)
• ac7e2e0b11be16a8e3630efc4941a220d31bd9d6: style: return error instead of bool type (#3169) (@fengxsong)
• 2b964edf8e6e6b71f606058d4b9adfe93cf75411: update doc. (#3196) (@zzjin)
• 9c20dacb539d0063053d4665116d1f21b42edb44: 🤖 add release changelog using rebot. (#3134) (@sealos-release-rebot)

Full Changelog: https://github.com/labring/sealos/compare/v4.2.1-rc3...v4.2.1-rc4

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.

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

New Contributors

• @sakcer made their first contribution in https://github.com/labring/sealos/pull/3045

Full Changelog: https://github.com/labring/sealos/compare/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.

Sealos v4.2.1-rc1 🎉🎉

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

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

• 90b9a163eafe28c185a3e752cacda171872a9d57: feat: Add support for single-node mode without hosts in Clusterfile (#3024) (@LZiHaN)
• 1c6dd12c36754ec4cc75c9889fd852e45fdf0336: feat: open other app by sdk (#3011) (@c121914yu)

Bug fixes

• 16ab2d2c81a3d1312937aa21538763f9080ea2b6: bugfix: fix duplicate print prompts (#3020) (@nowinkeyy)

Other work

• 8783311762ac938eb035a5c6ef15baf3aecffd72: Automated Changelog Update: Update directory for v4.2.0 release (#2977) (@sealos-ci-robot)
• 9aa43c8b4f15a14c60153d7752a1141363b86772: Cluster image desktop (#3028) (@lingdie)
• 3cccfbaab4a99b023d28e2b684fec8b65172beb5: Replace all math/rand to safer crypto/rand. (#3031) (@zzjin)
• ff35c3e6ef8415067dace67c2256dd0750457a12: Stream log (#3018) (@c121914yu)
• 2d39bc86e7249a627ad01a7cdc799ea4a706bb19: Terminal controller support cors. (#2991) (@zzjin)
• 015f9c54c4074ac18e8541fb59c2593fdb823b42: Update README, add the new version UI showcase. (#3040) (@fanux)
• d528d6be713b9b9cf92169e5822d354d29fffb9d: add auth cluster image and update workflow (#2981) (@lingdie)
• df615299d952dac6ad03d59cadf3775088ff86e8: add systemDB design (#2955) (@fanux)
• 6f1bbae0a14f0fe9beb5c0a8b14db6e4f0ab1131: change cert env (#3033) (@lingdie)
• 6f0accc78c98843c171f1c2e6c725731fb8d0175: docs(main): add changelog action (#2990) (@cuisongliu)
• 6406b475674ffc030579e61c17ea71d99fa2281d: docs(main): add default image config.yml to config patch image (#3006) (@cuisongliu)
• c8d475710ab305cc20a272fe2010cfec284dd846: docs(main): add e2e test images (#3013) (@cuisongliu)
• a6e33bc799c2b760cad3ff38ad55afc02212f84b: docs(main): add image guide docs (#2992) (@cuisongliu)
• c552e68b0097c256202ac0566f2a6ec9b3037e9f: docs(main): e2e for core sealos (#3030) (@cuisongliu)
• 9f8189aa7a3131c716ed6a8d2887d1fad347c863: docs(main): e2e for image shim for sealos (#3034) (@cuisongliu)
• bb7e82da0380547aae9c456f3fa0aa1cd2a305bb: docs(main): fix bot config (#3021) (@cuisongliu)
• 453218412cac23039c9cbf74b61924d2dedbad54: docs(main): fix release comment (#2982) (@cuisongliu)
• 0d2588faf32e51c4467c66b106c4018276d73af6: docs(main): replace lookup env to apply (#3039) (@cuisongliu)
• 884dfb0845d00f65f49782c50127e321d85eb1fb: docs(main): save sealos for controllers (#3026) (@cuisongliu)
• e758ed41264cc71d99e366185f7d2d572aa3653c: docs(main): save sealos for controllers,front,service (#3029) (@cuisongliu)
• 4b5f9d794435f9f9835bf43ed74ccb4670ef2c55: docs(main): upgrade bot version (#3022) (@cuisongliu)
• 6e1db7b96a2d7631777677d0f728db3b03ad9b42: feat terminal add env ttyd image (#3012) (@zjy365)
• f8269fb07b215c76eee37ed6d08fd47ee4d14d34: feat terminal cors & decodeURIComponent url command (#2988) (@zjy365)
• 147ed6d372d3281f8a6e666db61572b07a46c5f3: feat web terminal frontend (#2972) (@zjy365)
• 22bdba549f669086556bf06e8080c8da1fa6d535: feat. build frontend cluster image (#3016) (@lingdie)
• 3a7970cc1b3512517020627bbaf4fdc2e5ab1af4: feature: using promptui replace confirm (#2993) (@nowinkeyy)
• 5feb91b71a25eed7ef534e87963a88bc99c2dddd: fix GetHostArch without use args port (#3042) (@ghostloda)
• e71f980be1d586648b757d6938c8113e7ad1897e: fix sha len not same (#3025) (@lingdie)
• d4f5eb26752a5cdc291bc36b992147715c6feffa: fix sync tag name (#3015) (@lingdie)
• b68437084ba4a3b8de520b258332469c2dfeaa17: fix. cluster image controller (#3017) (@lingdie)
• d57b729566c85aee12065a3d0f0388b4424c021c: new app: launchpad (#2987) (@c121914yu)
• f8774d06b944655a16fbcc1f65f31f1c5d6c4c5e: update controller and service cluster image build (#3001) (@lingdie)

Full Changelog: https://github.com/labring/sealos/compare/v4.2.0...v4.2.1-rc1

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.

Sealos v4.2.0 🎉🎉

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

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/scripts/install.sh \
    | sh -s v4.2.0 labring/sealos

Yum Repository Installation

Add the following content to the /etc/yum.repos.d/sealos.repo file：

[sealos]
name=Sealos Repository
baseurl=https://yum.repo.sealos.io/
enabled=1
gpgcheck=0

Then run:

yum install sealos

APT Repository Installation

Add the following content to the /etc/apt/sources.list.d/sealos.list file：

deb [trusted=yes] https://apt.repo.sealos.io/ /

Then run:

apt-get update
apt-get install 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

• ef9d393890ffad3eacddf03b736324bb5ac0a4d0: feat: add infra metering implementation with e2e test (#2797) (@xiaohan1202)

Other work

• aa72e131e7a0dc28e0ed3d096489709cc6c4b2ae: Automated Changelog Update: Update directory for v4.2.0-alpha3 release (#2964) (@sealos-ci-robot)
• e26332d3fedc8c684481515e64d7a3fce7b2be9f: docs(main): delete build sealos image (#2975) (@cuisongliu)
• f696a621e5a91ce771b725e8b465f7f84f2aaa13: docs(main): fix bot config (#2976) (@cuisongliu)
• 8a521506e2c8b335225af8f24c3e61c5aca9d0a2: docs(main): fix change owner (#2973) (@cuisongliu)
• 967baa6b081135e7579a74d9b45e82247401227c: docs(main): fix change owner (#2974) (@cuisongliu)
• 8679b13f08dce0c72cb1ae5bd66e05e0ca1474a0: docs(main): fix changelog for sealos (#2963) (@cuisongliu)
• 908039e028e6128a7ff62f5a1099fd251d97599f: docs(main): fix ci patch images (#2971) (@cuisongliu)
• fa1776069c2633e02f072eb814a225ff02c737d6: docs(main): fix image0 to scratch (#2969) (@cuisongliu)
• 8e1d6afebc1e816412ad98382d8abc194bb2f9e5: docs(main): fix run workflow to test-run (#2970) (@cuisongliu)
• fa063c1fa9c68c473a395d94f12b17d3270d8737: docs: upgrade bot config (#2968) (@cuisongliu)

Full Changelog: https://github.com/labring/sealos/compare/v4.2.0-alpha3...v4.2.0

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.

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

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

Bug fixes

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

Other work

• 89a519b55ecf9c266f55953d5a84ed0270d1fda3: E2e/apply test workflow (#2952) (@bxy4543)
• 31e40627dc8db35dfa2681804b2b895c653bcc1e: Fix login ingress deploy (#2909) (@zzjin)
• 9b7fd80b7659f57e87b2b9f09e8e103e575a2e14: Move deploy doc. (#2951) (@zzjin)
• cdacf36cb0918462e6c517a342b00d40bd61295a: Reduce terminal limits a little. (#2915) (@zzjin)
• 5efa4b1c2d6748b8542ff3c6f958f7527350496b: Title: Update auto-release logic to skip deb and rpm packages for non-production releases (#2882) (@cuisongliu)
• 9725dedb5dde50e8bb6b04f975d17a1a97bce54d: add bytebase controller (#2841) (@dinoallo)
• 7ce51bb3074fbb8b2f4d9b8bd9c1ec20306c3f90: add e2e apply test (#2936) (@bxy4543)
• fba6b37728e840b15e41b5713d19d7438bcae479: add fetch Kubeadm Config: (#2943) (@bxy4543)
• b2ed4c7b9754091a4bf31311e8bda970101e8263: add image-cri-image test (#2849) (@bxy4543)
• 21cdb8bc7a3b9648e97a9ce006d47b3754af5541: add local deplopment docs. (#2945) (@lingdie)
• 8a67f568a58287dbe2d0108fbb0c9d20598cb00d: ci，docs: add account e2e test and docs (#2935) (@xiao-jay)
• 2d8d793e7eaa338aa8261075d6b16596cb06f1cd: docs(main): Refactor Changelog generation script and update usage guide (#2884) (@cuisongliu)
• 72a58a94031eb8ceadcd35aca3c67df43bbf8cea: docs(main): add changelog full to shell (#2885) (@cuisongliu)
• 53974f5e7498593af7384c0a77062f551311711a: docs(main): add debug for merge logger (#2886) (@cuisongliu)
• a100d1a5d4136369b49dfefb02e1dda58203ceba: docs(main): add docs for sealctl (#2922) (@cuisongliu)
• c781a29e50c45a57254c66eb7a09c25013d9ffd9: docs(main): add docs for user (#2929) (@cuisongliu)
• e5a204154f236622aebcccc51ba10df5f32d84b0: docs(main): add image-cri-shim docs (#2880) (@cuisongliu)
• de11f2b790efa907a4c62c4e934ba16a60e594a0: docs(main): add robot for sealos (#2959) (@cuisongliu)
• 42e06f9ea34e7db1edee1277f2050601ffd5940b: docs(main): support v1.27 docs (#2939) (@cuisongliu)
• 60b038828da1ac2b0e915789b311104e05149d6c: docs(main): support v1.27 k8s (#2938) (@cuisongliu)
• 8c4a998bb45d48396878a28ff690c286a95720d2: docs(main): sync code user and email (#2900) (@cuisongliu)
• 18b344744a4df5c387c7323818b3c655ad805bd8: docs(main): update gorelease config for new release (#2953) (@cuisongliu)
• a929e01b639a409d03c9db06694f9a01e0fcb936: docs(main): upgrade gomod (#2894) (@cuisongliu)
• 696c7415e2f196dd40722fb8ee4bfc53df5924e7: docs: how to write reousrce-controller (#2941) (@xiao-jay)
• e43c77cbf38e1d6fb4bd591621323a40e0e6a51e: docs: translate metering design from CN to EN (#2746) (@xiao-jay)
• b49983dc993b0ffe0ac33b7f84a3589ec9c9afd4: feat add bytebase application (#2925) (@zjy365)
• c93c368967bf38061d3ff7bf8b5371554a75414e: feature: support checking cluster's no-odd number of master node (#2842) (@pixeldin)
• 9ca8b5e54d592c69aa33676f1540d575ee055c5a: feature: support pulling multiple images at the same time (#2931) (@dhanusaputra)
• 9256d27ef8f0d840f44f02526f64e46437b74695: fix len(deleteInstancesByOption.instanceIds) always gt 0 (#2934) (@bxy4543)
• 3018f694ebfdb918f1a577d9dffe59afd03cc578: fix multi infra apply (#2960) (@bxy4543)
• 7fd1373459b7e1172f1f6f6fe2281271b79c914f: fix notification (#2895) (@zjy365)
• 2fc130bec22217eb015b777ab48f971f97838834: fix pgsql status null (#2924) (@zjy365)
• a26403fc794a015d97f89996e0431b3f7219388f: fix stop kube-apiserver pod cause DeadlineExceeded when update cert. (#2918) (@bxy4543)
• 86e8983b62d5296c3908ad3e4b8bc252cd620716: fix sync docs error (#2944) (@xiao-jay)
• be282f8d12d25570ea8bb4171300889ee240cf80: format(account): format webhook name (#2928) (@xiao-jay)
• 168319f56bfecffbbf819b32c97d5fa487eaf691: optimize reset node ip link delete command. (#2947) (@bxy4543)
• 7c66fd20cf6c424c4cc492bf119c38115d72c141: refactor: add back auto build and auto save abilities in diff command (#2906) (@fengxsong)
• 187be92fc0d62898683db58725a6a9a79cf7bb76: refactor: diff command (#2879) (@fengxsong)

Full Changelog: https://github.com/labring/sealos/compare/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.

Usage

# 下载并安装sealos, sealos是个golang的二进制工具，直接下载拷贝到bin目录即可, release页面也可下载
wget  https://github.com/labring/sealos/releases/download/v4.2.0-alpha2/sealos_4.2.0-alpha2_linux_amd64.tar.gz  && \
    tar -zxvf sealos_4.2.0-alpha2_linux_amd64.tar.gz sealos &&  chmod +x sealos && mv sealos /usr/bin
# 创建一个集群
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

Docker images

sealos:

docker pull ghcr.io/labring/sealos:v4.2.0-alpha2

lvscare:

docker pull ghcr.io/labring/lvscare:v4.2.0-alpha2

APT 源

Use your public APT Repository URL to install DEB packages:

https://apt.fury.io/labring/

To enable, add the following file /etc/apt/sources.list.d/fury.list:

deb [trusted=yes] https://apt.repo.sealos.io/ /

Yum源

Use your public YUM Repository URL to install RPM packages:

https://yum.fury.io/labring/

To enable, add the following file /etc/yum.repos.d/fury.repo:

[fury]
name=Gemfury Private Repo
baseurl=https://yum.repo.sealos.io/
enabled=1
gpgcheck=0

See the CHANGELOG for more details.

Usage

# 下载并安装sealos, sealos是个golang的二进制工具，直接下载拷贝到bin目录即可, release页面也可下载
wget  https://github.com/labring/sealos/releases/download/v4.2.0-alpha1/sealos_4.2.0-alpha1_linux_amd64.tar.gz  && \
    tar -zxvf sealos_4.2.0-alpha1_linux_amd64.tar.gz sealos &&  chmod +x sealos && mv sealos /usr/bin
# 创建一个集群
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

Docker images

sealos:

docker pull ghcr.io/labring/sealos:v4.2.0-alpha1

lvscare:

docker pull ghcr.io/labring/lvscare:v4.2.0-alpha1

APT 源

Use your public APT Repository URL to install DEB packages:

https://apt.fury.io/labring/

To enable, add the following file /etc/apt/sources.list.d/fury.list:

deb [trusted=yes] https://apt.repo.sealos.io/ /

Yum源

Use your public YUM Repository URL to install RPM packages:

https://yum.fury.io/labring/

To enable, add the following file /etc/yum.repos.d/fury.repo:

[fury]
name=Gemfury Private Repo
baseurl=https://yum.repo.sealos.io/
enabled=1
gpgcheck=0

See the CHANGELOG for more details.

Usage

# 下载并安装sealos, sealos是个golang的二进制工具，直接下载拷贝到bin目录即可, release页面也可下载
wget  https://github.com/labring/sealos/releases/download/v4.1.7/sealos_4.1.7_linux_amd64.tar.gz  && \
    tar -zxvf sealos_4.1.7_linux_amd64.tar.gz sealos &&  chmod +x sealos && mv sealos /usr/bin
# 创建一个集群
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

Docker images

sealos:

docker pull ghcr.io/labring/sealos:v4.1.7

lvscare:

docker pull ghcr.io/labring/lvscare:v4.1.7

APT 源

Use your public APT Repository URL to install DEB packages:

https://apt.fury.io/labring/

To enable, add the following file /etc/apt/sources.list.d/fury.list:

deb [trusted=yes] https://apt.repo.sealos.io/ /

Yum源

Use your public YUM Repository URL to install RPM packages:

https://yum.fury.io/labring/

To enable, add the following file /etc/yum.repos.d/fury.repo:

[fury]
name=Gemfury Private Repo
baseurl=https://yum.repo.sealos.io/
enabled=1
gpgcheck=0

See the CHANGELOG for more details.

What's Changed

• fix(main): delete node not exec clean.sh by @cuisongliu in https://github.com/labring/sealos/pull/2759

Full Changelog: https://github.com/labring/sealos/compare/v4.1.5...v4.1.7

Usage

# 下载并安装sealos, sealos是个golang的二进制工具，直接下载拷贝到bin目录即可, release页面也可下载
wget  https://github.com/labring/sealos/releases/download/v4.1.6/sealos_4.1.6_linux_amd64.tar.gz  && \
    tar -zxvf sealos_4.1.6_linux_amd64.tar.gz sealos &&  chmod +x sealos && mv sealos /usr/bin
# 创建一个集群
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

Docker images

sealos:

docker pull ghcr.io/labring/sealos:v4.1.6

lvscare:

docker pull ghcr.io/labring/lvscare:v4.1.6

APT 源

Use your public APT Repository URL to install DEB packages:

https://apt.fury.io/labring/

To enable, add the following file /etc/apt/sources.list.d/fury.list:

deb [trusted=yes] https://apt.repo.sealos.io/ /

Yum源

Use your public YUM Repository URL to install RPM packages:

https://yum.fury.io/labring/

To enable, add the following file /etc/yum.repos.d/fury.repo:

[fury]
name=Gemfury Private Repo
baseurl=https://yum.repo.sealos.io/
enabled=1
gpgcheck=0

See the CHANGELOG for more details.

Full Changelog: https://github.com/labring/sealos/compare/v4.1.5...v4.1.6

Usage

# 下载并安装sealos, sealos是个golang的二进制工具，直接下载拷贝到bin目录即可, release页面也可下载
wget  https://github.com/labring/sealos/releases/download/v4.1.5/sealos_4.1.5_linux_amd64.tar.gz  && \
    tar -zxvf sealos_4.1.5_linux_amd64.tar.gz sealos &&  chmod +x sealos && mv sealos /usr/bin
# 创建一个集群
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

Docker images

sealos:

docker pull ghcr.io/labring/sealos:v4.1.5

lvscare:

docker pull ghcr.io/labring/lvscare:v4.1.5

APT 源

Use your public APT Repository URL to install DEB packages:

https://apt.fury.io/labring/

To enable, add the following file /etc/apt/sources.list.d/fury.list:

deb [trusted=yes] https://apt.repo.sealos.io/ /

Yum源

Use your public YUM Repository URL to install RPM packages:

https://yum.fury.io/labring/

To enable, add the following file /etc/yum.repos.d/fury.repo:

[fury]
name=Gemfury Private Repo
baseurl=https://yum.repo.sealos.io/
enabled=1
gpgcheck=0

See the CHANGELOG for more details.

Usage

# 下载并安装sealos, sealos是个golang的二进制工具，直接下载拷贝到bin目录即可, release页面也可下载
wget  https://github.com/labring/sealos/releases/download/v4.1.5-rc3/sealos_4.1.5-rc3_linux_amd64.tar.gz  && \
    tar -zxvf sealos_4.1.5-rc3_linux_amd64.tar.gz sealos &&  chmod +x sealos && mv sealos /usr/bin
# 创建一个集群
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

Docker images

sealos:

docker pull ghcr.io/labring/sealos:v4.1.5-rc3

lvscare:

docker pull ghcr.io/labring/lvscare:v4.1.5-rc3

APT 源

Use your public APT Repository URL to install DEB packages:

https://apt.fury.io/labring/

To enable, add the following file /etc/apt/sources.list.d/fury.list:

deb [trusted=yes] https://apt.repo.sealos.io/ /

Yum源

Use your public YUM Repository URL to install RPM packages:

https://yum.fury.io/labring/

To enable, add the following file /etc/yum.repos.d/fury.repo:

[fury]
name=Gemfury Private Repo
baseurl=https://yum.repo.sealos.io/
enabled=1
gpgcheck=0

See the CHANGELOG for more details.