Service/cluster/routing discovery component about pilot HOT 8 CLOSED

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.

from pilot.

We should utilize SDS and/or CDS if the proxy provides this capability.
(see envoyproxy/envoy#144 (comment))

from pilot.

from pilot.

#29 addresses service registration side.
I realized there is a complication with multi-port services while implementing this.
We probably need multiple clusters for each named port in a service.

from pilot.

#32 addresses the proxy static configuration.

from pilot.

@kyessenov is the service discovery component going to be part of the istio project that the envoy-istio proxy will be consuming ?

from pilot.

Yes, that's correct. There are three pieces: SDS, envoy/istio proxy talking to SDS, envoy/istio proxy agent (responsible for reloading configs).

from pilot.

Cool.. It would great if you could point me to any code/design documentation related to the SDS.

from pilot.