Open mbarlow opened 4 years ago
@mbarlow Can you try with the latest rc2? In this release I have updated gloo to the latest release. Looks like a bug on their side.
@StrongMonkey upgraded to rc2. Retried same steps. I'm still not getting the body response from settings on 404
Describe the bug
Following the instructions here: https://docs.solo.io/gloo/latest/guides/traffic_management/configuration_validation/invalid_route_replacement/ (modify for rio-system namespace) does not result in invalid route handling by gloo. Confirmed settings for "replaceInvalidRoutes" is set to true by doing:
kubectl get settings -n gloo-system default -oyaml
To Reproduce
install rio w/ clusterdomiain & deploy a workload. Verify accessing your workload.
Patch gloo settings.
kubectl patch settings -n rio-system default --patch '{"spec": {"gloo": {"invalidConfigPolicy"{"replaceInvalidRoutes": true}}}}' --type=merge
Modify workload URL and specify a path that does not exist on workload, or just hit a fictional sub/subdomain on your domain.
See that response body is not the value from gloo settings. If changing response code, see that it is not honoring value. 404 returns. Response body is empty
Expected behavior Response body for any bad routes will be replaced with settings value in gloo.
Kubernetes version & type (GKE, on-prem):
kubectl version
Type: Rio version:
rio info
Additional context
rio system logs
output: