create prepare_one_node_cluster command

[wanghanchengchn]

Summary

To better support the deployment and management of single-node Kubernetes clusters, I have created a new command prepare_one_node_cluster. Previously, the create_one_node_cluster command was responsible for both preparing the single-node environment and setting up the master node. Now, I have added a new command called prepare_one_node_cluster. With this new command, users can first prepare the single-node environment, and then manually run setup_master_node to set up the master node when needed. This increased flexibility enables users to selectively execute the relevant steps based on their specific needs.

Implementation Notes ⚒️

First, I have split the create_one_node_cluster command into two parts: preparing the single-node environment and setting up the master node. Note that I have only divided the previous create_one_node_cluster command into two functions, without affecting the functionality of the original create_one_node_cluster command.

Subsequently, I have created the prepare_one_node_cluster command, which only runs the first part of the create_one_node_cluster command, i.e., the part responsible for preparing the single-node environment. After running the prepare_one_node_cluster command, users can manually call the setup_master_node command when they need to.

External Dependencies 🍀

N/A

Breaking API Changes ⚠️

N/A

[lrq619]

Hi hancheng, please pass the unit test there

[JooyoungPark73]

The reason why runner is failing is because we use create one node cluster on other function.

vHive/scripts/cloudlab/start_onenode_vhive_cluster.go

Line 121 in cc52682

if err := cluster.CreateOneNodeCluster(sandbox); err != nil {

Please add setup master node there and re-run the checks.

[lrq619]

Please rebase on the main branch and check if all checks are passed

[lrq619]

Looks fine to me