Replies: 2 comments 1 reply
-
Thanks for opening this, @kyzrfranz, happy we could have this discussion in triaging a potential issue. May I ask you to provide further logs in order to evaluate if it's a valid bug, or not? |
Beta Was this translation helpful? Give feedback.
0 replies
-
Certainly, so this is from the second run:
caused by setting up the tcp manager a second time I did a quick hack to verify if it is indeed the issue:
This did in fact mitigate, but not sure if it's a real solution ;) |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I don't quite know if this is actually an issue but during testing I encountered the following behavior:
With
ExternalClusterReference
enabled:then the ExternalClusterReferenceReconciler will try to setup the TCP controller again running into an error. Only a restart will fix this. Is this intentional?
I did check a quick hack to just ignore the error for "blah blah .. duplicate tcp controller .. blah blah" and it went about it's busines fine.
wdyt?
Beta Was this translation helpful? Give feedback.
All reactions