Jiezhang Wang
Jiezhang Wang
> Failed to ensure portal This log does not affect EdgeMesh usage. This error log just because both kube-proxy and edgemesh handle nodePort-type services.
Can you print some edgemesh-agent logs when you exec `nslookup xxx` command?
There are two ways to fix your problem, you can choose one: 1. deploy edgemesh-agent to your master node(default-control-plane): ``` kubectl taint nodes --all node-role.kubernetes.io/master- ``` 2. Filter kube-dns service...
Are you enabled the cacheDNS?
> kubectl label services -n kube-system kube-dns service.edgemesh.kubeedge.io/service-proxy-name- If you enable the cacheDNS, then you must proxy kube-dns.
No, the documentation has no corresponding instructions. You're right, I'll add the documentation later.
cacheDNS requires you to specify the upstream dns nameserver yourself, for example: ``` 10.96.0.10 --> coredns cluster ip 100.125.3.250 --> your custom dns ``` When edgemesh's dns runs in cacheDNS...
> So basically cacheDNS is just a setting that allows to configure some fallback DNS servers in case the clusterDNS isn't reachable? So in my case not needed, right? You...
You can try to depolyment `Prometheus、Node_Exporter、PushGateway` in your kubeedge cluster.
这样的修改是合理的，你看能不能将你的修改提交成PR?