Armin Schlegel
Armin Schlegel
@Poorunga rebased this PR on lastest master after #390 and updated edgemesh helm package as well.
@Poorunga would you do a review again?
@Poorunga modifed according your suggetions. Please take another look
@Poorunga done squashing all commits
Well, then i'd have no problem labeling those edge services. On the other hand, the current behavior breaks the whole cluster DNS if the label is not set.
For better configuration i propose something like follows. I'd offer this feature with a new configuration option: 1. There is an option that tells: invert the current label behavior. I...
> Can you print some edgemesh-agent logs when you exec `nslookup xxx` command? Sure, ``` E1010 08:41:42.400357 1 loadbalancer.go:683] "Dial failed" err="get proxy stream from default-control-plane error: new stream between...
@Poorunga thanks! I think the issue is solved by ignoring the kube-dns service. I opened a new issue #389 that targets the original problem with the setup.
@Poorunga I just provisioned a RPI device and see strange behavior when resolving to both service and external hosts Here you see logs of nslookup on www.google.com from the issuing...
Yes, i enabled cacheDNS