contour: IngressRoute support for custom request timeout
Describe the solution you’d like I’d like to be able to configure custom request timeouts per IngressRoute.
It seems from docs that you can use annotations on ingresses, but according to this comment
IngressRoutes don’t really use annotations for anything
Docs regarding IngressRoute contain no reference to a requests timeout config parameter.
Environment:
- Kubernetes version: v1.10.3 (EKS)
- Cloud provider or hardware configuration: AWS
Contour daemon set
apiVersion: extensions/v1beta1
kind: DaemonSet
metadata:
labels:
app: contour
name: contour
namespace: heptio-contour
spec:
selector:
matchLabels:
app: contour
template:
metadata:
annotations:
prometheus.io/format: prometheus
prometheus.io/path: /stats
prometheus.io/port: "9001"
prometheus.io/scrape: "true"
creationTimestamp: null
labels:
app: contour
spec:
containers:
- args:
- serve
- --incluster
command:
- contour
image: gcr.io/heptio-images/contour:latest
imagePullPolicy: Always
name: contour
ports:
- containerPort: 8000
hostPort: 8000
name: contour
protocol: TCP
- args:
- --config-path /config/contour.yaml
- --service-cluster cluster0
- --service-node node0
- --log-level info
- --v2-config-only
command:
- envoy
image: docker.io/envoyproxy/envoy-alpine:v1.7.0
name: envoy
ports:
- containerPort: 8080
hostPort: 8080
name: http
protocol: TCP
- containerPort: 8443
hostPort: 8443
name: https
protocol: TCP
volumeMounts:
- mountPath: /config
name: contour-config
dnsPolicy: ClusterFirst
hostNetwork: true
initContainers:
- args:
- bootstrap
- /config/contour.yaml
command:
- contour
image: gcr.io/heptio-images/contour:latest
imagePullPolicy: Always
name: envoy-initconfig
volumeMounts:
- mountPath: /config
name: contour-config
restartPolicy: Always
serviceAccount: contour
serviceAccountName: contour
volumes:
- emptyDir: {}
name: contour-config
About this issue
- Original URL
- State: closed
- Created 6 years ago
- Comments: 15 (14 by maintainers)
Commits related to this issue
- design: Support Custom Request Timeout Updates #815 Signed-off-by: Prasoon Telang <telangp@vmware.com> — committed to prasoontelang/contour by deleted user 5 years ago
- design: Support Custom Request Timeout Updates #815 Signed-off-by: Prasoon Telang <telangp@vmware.com> — committed to prasoontelang/contour by deleted user 5 years ago
- design: Support Custom Request Timeout Updates #815 Signed-off-by: Prasoon Telang <telangp@vmware.com> — committed to prasoontelang/contour by deleted user 5 years ago
- design: Support Custom Request Timeout Updates #815 Signed-off-by: Prasoon Telang <telangp@vmware.com> — committed to prasoontelang/contour by deleted user 5 years ago
- design: Support Custom Request Timeout Updates #815 Signed-off-by: Prasoon Telang <telangp@vmware.com> — committed to prasoontelang/contour by deleted user 5 years ago
- support custom request timeout via ingressroute Updates #815 Users can set timeout policy and retry policy for each route matched under ingressroute. Signed-off-by: Prasoon Telang <telangp@vmware.c... — committed to prasoontelang/contour by deleted user 5 years ago
- design: add a stramman design for backend TLS verification Updates #815 This PR adds a draft design for validation of backend services accessed over TLS. Signed-off-by: Dave Cheney <dave@cheney.net... — committed to davecheney/contour by davecheney 5 years ago
I am willing to work on this if nobody is actively working. Will start with the design doc.
At a first pass thinking about how this configuration should be exposed I think Retry and Timeout parameters should be segregated into different types; eg.
route: match: /slow retry: count: 7 retryon: - 50x timeout: connect: 500ms response: 2s
On Sun, 27 Jan 2019 at 10:01, Robert Syvarth notifications@github.com wrote: