-
Notifications
You must be signed in to change notification settings - Fork 2.8k
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
clustermesh: document global services limitations with KPR=false #31798
clustermesh: document global services limitations with KPR=false #31798
Conversation
/test |
BTW I would expect that the new endpointslice sync feature most likely lift this limitation as well (IIUC?) as the remote clusters endpoints would be available to kube proxy, although that's maybe too niche/new to mention it here? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks
Yep, that's my expectation as well. I'd personally merge this version first so that it can be backported to stable branches, and then mention that as part of a follow-up. WDYT? |
Global services do not work when KPR is disabled if accessed through a NodePort, or from a host-netns pod, as kube-proxy doesn't know about the remote backends. Let's explicit these limitations. Signed-off-by: Marco Iorio <marco.iorio@isovalent.com>
f75ca63
to
3a31bc4
Compare
Rebased onto main as one of the workflows appears to have been renamed. |
/test |
Global services do not work when KPR is disabled if accessed through a NodePort, or from a host-netns pod, as kube-proxy doesn't know about the remote backends. Let's explicit these limitations.