enroute
enroute copied to clipboard
saarasio
EnRoute Ingress API Gateway - Kubernetes-native, Ingress API Gateway Powered using Envoy
Splits demo service-policy and actual service policy templates so that users can deploy "real" service-policies from helm.
If service is absent, a default value is created with uninitialized values. When we attach a route to a service, we need to add validation to check if the service...
The following proxy config has two gRPC upstreams. However the protocol is not shown in output of dump command - ``` $ curl -s 127.0.0.1:1323/proxy/dump/gw | jq { "data": {...
Note below that a route got created without a name. However we should be able to delete this route ``` ubuntu@ip-172-31-30-70:~/enroute/packaging$ curl -s localhost/service/adminservice/route -H "Authorization: Bearer treehugger" | jq...
Currently, the following upstream fields read from the cloud are not programmed for Envoy. Need to add support for these fields. ``` "upstream_strategy": null, "upstream_validation_cacertificate": null, "upstream_validation_subjectname": null, ```
Right now upstream ports are set to values provided by contour. They are not configurable. This value needs to be configurable from the webapp API
Route id is a foreign key in route_upstream relationship table. Entry in this table should be deleted before the route is deleted. When a route delete call is made, we...
For PATCH calls, Content-Type should be set to application/json when making such API calls. However, when it is missing, updates fail and there is no error message. There should be...
Note that when upstream_ip is not provided, the error message is - "No JSON object could be decoded". This is not very helpful. ``` [ec2-user@ip-172-31-18-10 enroute-cp]$ curl -s -X POST...