[x] Like egctl of the Easegress, the global parameter support is needed by emctl.
[x] We are used to deploying easemesh control plane in a K8s cluster via emctl install command, as far as we knew the service of control plane was exposed as a NodePort. In general, the port listened on nodes is a random port, so when we install easemesh control plane, the emctl command can preserve the random port as a global --server option. In another word, the global --server option in ${HOME}/.emctlrc is generated by emctl install command.
For now, we just support --server option, it is an endpoint for the EaseMesh control plane. Global options can be saved in${HOME}/.emctlrc file
I've two requirement:
egctl
of the Easegress, the global parameter support is needed byemctl
.emctl install
command, as far as we knew the service of control plane was exposed as aNodePort
. In general, the port listened on nodes is a random port, so when we install easemesh control plane, the emctl command can preserve the random port as a global--server
option. In another word, the global--server
option in ${HOME}/.emctlrc is generated byemctl install
command. For now, we just support--server
option, it is an endpoint for the EaseMesh control plane. Global options can be saved in${HOME}/.emctlrc
file