-
Notifications
You must be signed in to change notification settings - Fork 91
Service/cluster/routing discovery component #3
Comments
This component should be capable of being run as a separate service or as part of the Manager Service. For proxies that fetch service information remotely (e.g., Envoy), this component would provide a generic discovery API. For proxies that cannot fetch such information at runtime (e.g., Nginx, Haproxy), this component would generate the static configuration file containing the IP addresses per service. |
We should utilize SDS and/or CDS if the proxy provides this capability. |
Right. This is the API that needs to be exposed by this component.
On Wed, Dec 14, 2016 at 7:37 PM Kuat ***@***.***> wrote:
We should utilize SDS and/or CDS if the proxy provides this capability.
(see envoyproxy/envoy#144 (comment)
<envoyproxy/envoy#144 (comment)>)
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#3 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AH0qdwAlVeJmMqlBgU3XIILlqWtAOptyks5rIIvTgaJpZM4LJfr8>
.
--
~shriram
|
#29 addresses service registration side. |
#32 addresses the proxy static configuration. |
@kyessenov is the service discovery component going to be part of the istio project that the envoy-istio proxy will be consuming ? |
Yes, that's correct. There are three pieces: SDS, envoy/istio proxy talking to SDS, envoy/istio proxy agent (responsible for reloading configs). |
Cool.. It would great if you could point me to any code/design documentation related to the SDS. |
We need to provide an abstraction layer over the service network for the proxy configuration that can enumerate services and their IP endpoints and work cross-platform.
Although this information is not a user-provided intent but the platform-specific status, Manager should encapsulate this for Istio Proxy.
The text was updated successfully, but these errors were encountered: