Skip to content
This repository has been archived by the owner on Sep 5, 2024. It is now read-only.

requestTimeoutSeconds only affects version specific services in Gloo #1031

Closed
r2ewj opened this issue Apr 23, 2020 · 2 comments
Closed

requestTimeoutSeconds only affects version specific services in Gloo #1031

r2ewj opened this issue Apr 23, 2020 · 2 comments
Assignees
Labels
bug Something isn't working

Comments

@r2ewj
Copy link

r2ewj commented Apr 23, 2020

I created a new service via Riofile with a timeout:

services:
ido-ui:
requestTimeoutSeconds: 120

This creates 4 VirtualServices in Gloo, I've noticed that the version specific services receive the Timeout option, but the main end point does not.
ido-ui-v0 has the timeout
ido-ui-v0-tls-#####.on-rio.io-tls has the timeout
ido-ui-tls-####.on-rio.io-tls no timeout
ido-ui no timeout
This is the expected result from ido-ui-v0:
spec:
virtualHost:
domains:
- ido-ui-v0-rf.####.on-rio.io
routes:
- matchers:
- prefix: /
options:
timeout: 120s
routeAction:
single:
kube:
port: 80
ref:
name: ido-ui-v0
namespace: rf

This is the result from the non versioned service
spec:
virtualHost:
domains:
- ido-ui-rf.#####.on-rio.io
routes:
- matchers:
- prefix: /
routeAction:
single:
kube:
port: 80
ref:
name: ido-ui-v0

@StrongMonkey
Copy link
Contributor

Should be fixed in v0.7.1-rc2.

@StrongMonkey
Copy link
Contributor

@r2ewj I will close this issue since it should have been fixed in v0.7.1. Feel free to reopen if you still see it.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants