camper42 commented on PR #5062: URL: https://github.com/apache/kyuubi/pull/5062#issuecomment-1643443469
headless service `kyuubi-headless.kyuubi.svc.cluster.local` will resolve to: - Pod 0 IP - Pod 1 IP - ... - Pod N IP --- Pod DNS(stable network ID) will resolve to Pod IP: - kyuubi-0.kyuubi-headless.kyuubi.svc.cluster.local -> Pod 0 IP - kyuubi-1.kyuubi-headless.kyuubi.svc.cluster.local -> Pod 1 IP - ... - kyuubi-N.kyuubi-headless.kyuubi.svc.cluster.local -> Pod N IP --- Cluster IP/External IP will proxy to one Pod IP (and stick for a client IP if sessionAffinity enabled) --- in the current implementation, no difference between service expose methods for kyuubi REST ? > - the response contains the Kyuubi-Server-1 Pod address > - the client always(until network exception) tries to access the Kyuubi-Server-1 directly to avoid Kyuubi Server internal forwarding overhead. in this implementation, client needs to reconnect to the Kyuubi-Server-1 Pod address, if using HTTP, client can connect by Pod IP address, but if using HTTPS, we need a stable address? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
