Cloudcore is exist when I init it. and I can't find cloudcore.yaml in /etc/kubeedge/config

[sysu18364028]

Cloudcore is exist when I init it. and I can't find cloudcore.yaml in /etc/kubeedge/config Command: root@k8scludes1:~# sudo keadm init --advertise-address=192.168.88.130 --kubeedge-version=1.12.1 --kube-config=/root/.kube/config the report message are as follow: Error: CloudCore is already running on this node, please run reset to clean up first Usage: keadm init [flags]

Examples:

keadm init

• This command will render and install the Charts for Kubeedge cloud component

keadm init --advertise-address=127.0.0.1 --profile version=v1.9.0 --kube-config=/root/.kube/config

• kube-config is the absolute path of kubeconfig which used to secure connectivity between cloudcore and kube-apiserver
  • a list of helm style set flags like "--set key=value" can be implemented, ref: https://github.com/kubeedge/kubeedge/tree/master/manifests/charts/cloudcore/README.md

Flags: --advertise-address string Use this key to set IPs in cloudcore's certificate SubAltNames field. eg: 10.10.102.78,10.10.102.79 -d, --dry-run Print the generated k8s resources on the stdout, not actual excute. Always use in debug mode --external-helm-root string Add external helm root path to keadm. -f, --files string Allow appending file directories of k8s resources to keadm, separated by commas --force Forced installing the cloud components without waiting. -h, --help help for init --kube-config string Use this key to set kube-config path, eg: $HOME/.kube/config (default "/root/.kube/config") --kubeedge-version string Use this key to set the default image tag --manifests string Allow appending file directories of k8s resources to keadm, separated by commas --profile string Set profile on the command line (iptablesMgrMode=external or version=v1.9.1) --set stringArray Set values on the command line (can specify multiple or separate values with commas: key1=val1,key2=val2)

execute keadm command failed: CloudCore is already running on this node, please run reset to clean up first

[Poorunga]

@sysu18364028 Cloudcore's configuration file, after version 1.9, should be placed in configmap and can be viewed through the following command:

kubectl -n kubeedge edit configmap cloudcore

[Poorunga]

This PR is suitable for moving to the kubeedg repo: https://github.com/kubeedge/kubeedge