Add docs for clusterset IP feature #1181
Conversation
tpantelis
requested review from
dfarrell07,
Oats87,
skitt,
sridhargaddam and
vthapar
as code owners
|
🤖 Created branch: z_pr1181/tpantelis/clusterset_ip |
tpantelis
force-pushed
the
clusterset_ip
branch
from
1bfdc7e
to
75f49b3
Compare
| Lighthouse DNS will return the cluster set virtual IP from queries instead of a constituent cluster IP address. However, Submariner | ||
| does not perform load balancing and relies on some external component to do so. |
There was a problem hiding this comment.
This gives the impression that the virtual IP won’t work unless the user does something else — is that so?
There was a problem hiding this comment.
yes. This is for Istio support - they need a VIP and will handle the rest. We could also not document this feature.
There was a problem hiding this comment.
How is the routing handled for the virtualIP? Are we adding any iptable rules to support the datapath?
Lighthouse DNS will return the cluster set virtual IP from queries instead of a constituent cluster IP address. However, Submariner does not perform load balancing and relies on some external component to do so.
Normally when we return the clusterIP itself (or the associated GlobalIngressIP) kube-proxy does the load-balancing once the remote traffic lands in the local cluster (where the service is exprted). Can you please eloborate how this use-case works with virtualIP?
There was a problem hiding this comment.
Currently we're not doing any routing. This feature currently will be used only by Istio and it will take care of routing. Current submariner connectivity doesn't support this use case.
This use case can also be used by someone using Lighthouse-only for MCS service discovery and using their own MCS controller for datapath.
There was a problem hiding this comment.
It seems to me that this should be documented because users could end up shooting themselves in the foot.
Can we make the caveat more general? It’s not just load balancing, it’s any kind of routing.
| Lighthouse DNS will return the cluster set virtual IP from queries instead of a constituent cluster IP address. However, Submariner | |
| does not perform load balancing and relies on some external component to do so. | |
| Lighthouse DNS will return the cluster set virtual IP from queries instead of a constituent cluster IP address. However, Submariner | |
| does not route this virtual IP and relies on some external component to do so. |
There was a problem hiding this comment.
Currently we're not doing any routing. This feature currently will be used only by Istio and it will take care of routing. Current submariner connectivity doesn't support this use case.
Can you point me to any links/doc on how this will be used in Istio?
There was a problem hiding this comment.
Can you point me to any links/doc on how this will be used in Istio?
The use case was presented on an App Eng Exchange call a few weeks ago. The only doc I know of is https://docs.google.com/document/d/1RXjvYTKMKDFM8KNI9X3HT5M6oqKKwkMde7GeuKLD93Q/edit#heading=h.7mxk48pcmgyk shared by Jacek Ewertowski.
There was a problem hiding this comment.
0.19.0 has been released so revisiting this PR. @sridhargaddam Have you been able to review the Istio use case?
User guide and subctl commands. Signed-off-by: Tom Pantelis <[email protected]>
tpantelis
force-pushed
the
clusterset_ip
branch
from
75f49b3
to
addbbc8
Compare
|
This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further |
|
This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further |
|
🤖 Closed branches: [z_pr1181/tpantelis/clusterset_ip] |
User guide and subctl commands.