-
Notifications
You must be signed in to change notification settings - Fork 333
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Duplicated listeners after federating a zone #9006
Comments
Reproduced once, but not too much useful information captured. This issue is a transitional state during the importing step of the federation:
complete data plane logs
|
There are no unusual logs generated in any control planes:
All of logs generated from above pods are regular entries. |
|
In my case, the problem does not go away. Some things I've noticed:
Regarding 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 |
What happened?
got:
after federating a zone with demo installed, @bartsmykla mentioned that this could be related to #6717 - that's why I assigned @jijiechen
Steps to reproduce:
kumactl export
The text was updated successfully, but these errors were encountered: