[FEATURE] Admiral RFC: Client API

[jwebb49]

Create a way for clients to set timeouts, retries, circuit breakers, faults, and time delays that only apply to that specific client of the service and no other clients. This API designs and introduction of a new type will prevent the client from having access to the more sensitive routing, security, and load balancing configuration used by the service and not relying on the service team to make changes on the client’s behalf.

Details

[aattuluri]

@jwebb49 Nice proposal!

Currently istio's merge semantics do not allow virtual services to be merged for sidecars (only allowed at Gateway). We need this before we can implement the proposed design. As far as I can think, we cannot achieve this without support in Istio.

Also, not clear about reusing the istio's API part, are you referring to an existing API or a new one that will be built? Would be good to clarify that.

[jwebb49]

@jwebb49 Nice proposal!

Currently istio's merge semantics do not allow virtual services to be merged for sidecars (only allowed at Gateway). We need this before we can implement the proposed design. As far as I can think, we cannot achieve this without support in Istio.

Also, not clear about reusing the istio's API part, are you referring to an existing API or a new one that will be built? Would be good to clarify that.

[jwebb49]

@aattuluri the goal would be to have one VirtualService and use logic in admiral to merge the Client type with the existing VirtualService (VS) and DestinationRule (DR). The part I am not sure about would be to place the merged VS and DR in the client namespace or override the services VS and DR.

I was thinking to reuse the existing Istio API and not wrap it. WDUT?