KubeKey v2.0.0

[24sama]

🎉KubeKey v2.0.0 is happening!🎉

Thanks everyone for your contributions and ideas to the current version of KubeKey!

But to make KubeKey even better, it's time to make a change.

KubeKey current problems:

• Offline installation is complicated;
• Task scheduling has less context;
• There some great requested features that's hard to land in the current version without breaking changes.

In order to solve these problems, we need to consider bumping a major version.

Currently, KubeKey v2.0.0 development branch is dev-v2.0.0. And task scheduling engine of KubeKey v2.0.0 has been basically refactoring completed. Most of the details are contained in this issue: #598

The design of KubeKey v2.0.0 is mainly based the module pattern. The following are the most important units of KubeKey v2.0.0:

• Action: The most basic unit. It represents one operation performed on one node;
• Task: The one that manages Action. It contains fields such as Action, nodes, whether to retry, whether to execute in parallel, etc. In short, it represents executing an Action on the specified nodes as required;
• Module: A unit that contains one or more related Task. Module is a module with specific and complete functions;
• Pipeline: It contains Modules combined in a certain order. It is the complete execution process of a KubeKey command. For example, Create Cluster Pipeline, Add Nodes Pipeline and so on.

This is a huge code refactoring. For users, the use of KubeKey v2.0.0 has not changed much, but due to the modularity of task scheduling, it is easier for developers to expand the functions of KubeKey.

We also hope that more contributors can participate in the development of KubeKey and make KubeKey even better together.:wave:

Please prepend issue titles with [KubeKey v2.0.0] to give us your thoughts and feedback.

Feel free to contribute there!