Local Up OpenYurt

    Then you can use to interact with your OpenYurt cluster.

    In summary, the local_up_openyurt.sh will use the local files under the openyurt work path to set up the cluster. And you can specify the behavior of the shell through setting environment variables.

    Note:

    1. The format of is 1.xx, other formats will not be accepted. The default KUBERNETESVERSION is 1.22.
    2. NODES_NUM should not be less than 2. Finally, the cluster will contains one control-plane node and NODES_NUM-1 woker nodes. The default NODES_NUM is 2.

    At last, Finally, OpenYurt components will be installed in kubernetes cluster, including ‘Yurthub’, ‘Yurt-Controller-Manager’, ‘Yurt-tunnel-Agent’ and ‘Yurt-Tunnel-Server’.

    By now, you’ve got the OpenYurt cluster at your local host and you can interact with it using . kind will automatically stored the kubeconfig at your KUBECONFIG path (default path is ${HOME}/.kube/config). If you already have the KUBECONFIG to interact with other clusters, kind will add a new context of openyurt cluster into the KUBECONFIG and automatically switch to it. You can manually switch back to the previous context using command . For more details, you can see the documentation. You can store the kubeconfig at another path through setting KIND_KUBECONFIG.

    KIND_KUBECONFIG represents the path to store the kubeconfig file of the cluster which is created by this shell. The default value is “$HOME/.kube/config”.

    1. NODES_NUM

    NODES_NUM represents the number of nodes to set up in the new-created cluster. There are one control-plane node and NODES_NUM-1 worker nodes. Thus, NODES_NUM must not be less than 2. The default value is 2.

    1. KUBERNETESVERSION

    KUBERNETESVERSION declares the kubernetes version the cluster will use. The format is “1.XX”. Now from 1.17 to 1.23 are supported. The default value is 1.22.