MEF Edge Log Refreshing
Symptom
After MEF Edge is successfully interconnected with CloudCore, edge_main generates a large number of messages. As a result, logs are refreshed.
edgecore proxy receive msg router: {Source: Destination:EdgeCore Option:query Resource:default/node/***}, route: {Source:edge_main Group:resource Operation:response Resource:default/node/***}
Cause Analysis
kube-controller-manager does not allocate CIDR to nodes, and EdgeCore continuously queries the node status until CIDR is allocated.
Solution
- Log in to the host where MEF Center is installed.
- Modify the kube-controller-manager configuration file and configure the startup parameters cluster-cidr and allocate-node-cidrs of kube-controller-manager.
The kube-controller-manager configuration file is usually named /etc/kubernetes/manifests/kube-controller-manager.yaml.
Example:
--cluster-cidr=192.168.0.0/16 --allocate-node-cidrs=true
Parent topic: FAQs