allow more configuration params for upstreams

[benishak]

• max_requests_per_connection
• connect_timeout
• upstream_connection_options
• health_checks

https://www.envoyproxy.io/docs/envoy/latest/api-v2/api/v2/cds.proto

[yuval-k]

the main thing here is allowing health_checks which is a pretty complicated data structure.
I need to figure out if we can 'passthrough' the envoy definition instead of redefining it as I don't think we can provided a better abstraction anyway.

[benishak]

it is okay to adf health check in later stage
does gloo register only ready pods to envoy?

[yuval-k]

Today gloo works by taking the Endpoints object of a Service (i.e. what ever is in kubectl get endpoints SERVICE_NAME -o yaml)
I think I can do the non health check stuff in a day or two (have to clear some other things off my plate).

[ilevine]

health checks is the only one remaining

[rickducott]

Most of this is done. The health check also appears to be worked on in another repo. Going to close this out as stale.