-
Notifications
You must be signed in to change notification settings - Fork 2.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature: Refactoring Sealos to Support k3s, k0s Runtime #2863
Comments
This issue has been automatically closed because we haven't heard back for more than 60 days, please reopen this issue if necessary. |
repen |
This issue has been automatically closed because we haven't heard back for more than 60 days, please reopen this issue if necessary. |
|
using sealos v4.4.0+ |
using sealos v4.4.0+ |
Problem Description
Sealos currently does not support the k3s runtime and requires the redesign of the runtime interface to avoid excessive coupling with the Processor and to add verification.
Here is a record of testing various k3s installation methods. If you're curious about k3s, be sure to read this note, as well as k3s • official and documentation, and its GitHub • open source address.
Solution
Design a new runtime interface
Redesign the runtime interface to avoid excessive coupling with the Processor and add verification.
Design ideas for the k3s runtime module
To support the k3s runtime, we need to add a new runtime module. This module needs to support the following functions:
Design the k3s directory and filesystem distribution using Sealos' image distribution logic
To support the k3s runtime, we need to use Sealos' image distribution logic to design the k3s directory and filesystem distribution of the k3s image.
Optimize the packaging of kubeadm and k3s binaries
To support the k3s runtime, we need to optimize the packaging of kubeadm and k3s binaries.
Provide unit test and CI flow to ensure code quality
To ensure code quality, we need to provide unit testing and CI flow.
Tasks
The text was updated successfully, but these errors were encountered: