SurgicalPool has no load balancing algorithm leading to "invalid-pool-load-balancing-algorithm" error #458
Description
Current behavior
LoadBalancing Algorithm was introduced for the RoutePool in the #428.
The load balancing algorithm was not passed to the SurgicalPool (included in the RouteOpts for the initialization).
Missing load balancing algorithm in the surgical pool leads to the error "invalid-pool-load-balancing-algorithm".
This error is intended validation for a pool load balancing algorithm.
An additional log parameter needs to be added for this error for error research simplification.
Desired behavior
The load balancing algorithm is also needed to be passed to the SurgicalPool (included in the RouteOpts for the initialization).
Reproduction Steps
When I curl an app with an x-cf-app-instance header
curl -v "https://example-app.com/" -H "x-cf-app-instance: app_id:instance_id"
The same curl without the instance header works properly.
Impact
The custom per-route load balancing algorithm feature is not finally released.
This error has no functional impact in routing behaviour.