-
Notifications
You must be signed in to change notification settings - Fork 558
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
4.x release. #2456
Comments
The First Version UI Page Main PageThe main page is divided into two configuration types: Resource Inventory and Task Workflow Resource InventoryThe resource inventory currently includes two categories:
Features of Resource Inventory:
Task WorkflowTask workflows include predefined tasks and custom tasks. Workflows are closely tied to the nodes and node groups in the resource inventory. It is recommended to perform validation checks before execution. Features of Task Workflow
In feature. it should be determined whether it is necessary to create a separate task creation page for each individual task. |
Your current KubeKey version
No response
Describe this feature
feature
Version 4.x will include the following features.
task templates
andexecution frameworks
.task templates
: Task templates are flexible and changeable. Can be existing cluster management functions (will be used as built-in templates), and other customized functions.execution frameworks
: The task framework can be executed on the command line or in a k8s cluster.why to change it
In the current version of Kubekey, adding or modifying commands requires submitting code changes and releasing a new version, which limits extensibility.
• Separation of tasks from the framework (like ansible)
• Support for GitOps (manage automated tasks through Git)
• Support for connector extensions
• Support for cloud-native automated bulk task management
Describe the solution you'd like
Now we have two branch to implement it. feature-ops and feature-ui. it will merge to master after Finish.
Additional information
No response
The text was updated successfully, but these errors were encountered: