Closed slonka closed 9 months ago
Reproduced once, but not too much useful information captured.
This issue is a transitional state during the importing step of the federation:
There are no unusual logs generated in any control planes:
All of logs generated from above pods are regular entries.
Triage: we could double-check this with upgrade 2.5.0 to 2.6.0 without any federation. Increase the number of listeners (by adding more services) to get a better chance of hitting this issue.
In my case, the problem does not go away. Some things I've noticed:
kuma.io/transparent-proxying-reachable-services
to avoid the error if the pod only needs services from the other zoneRegarding that last point, perhaps simply filtering out duplicate configs before sending them could be a quick fix?
@ttreptow does this still happen in 2.6.1 ? Seems like there were multiple things at play at the same time here.
I didn't see the issue this time when I upgraded from 2.5.2 to 2.6.1
I spoke too soon actually, I do still see the issue
@ttreptow Thanks for reporting.
Just wanted to confirm a few items. Do you have any headless serviecs in your mesh? On the services of the duplicated listeners, are there any properties different or interesting? Does this problem cause any actual traffic issue in your mesh? We are seeing this occurring on headless services, and this will be fixed in a coming patch release.
If headless services are not in your case and you don't mind, could you send us a copy of your dumpped envoy config? (Please remove any sensetive information like secrets, PII, etc). You may post it on this thread if you'd like, or you can also send it via email to team-mesh@konghq.com
. Thank you very much.
What happened?
got:
after federating a zone with demo installed, @bartsmykla mentioned that this could be related to https://github.com/kumahq/kuma/issues/6717 - that's why I assigned @jijiechen
Steps to reproduce:
kumactl export