-
Notifications
You must be signed in to change notification settings - Fork 8.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support proxy_next_upstream_timeout #4005
Support proxy_next_upstream_timeout #4005
Conversation
CookieDomain string `json:"cookieDomain"` | ||
CookiePath string `json:"cookiePath"` | ||
NextUpstream string `json:"nextUpstream"` | ||
NextUpstreamTimeout string `json:"nextUpstreamTimeout"` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why string
? Should be int
.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's a time
value according to the docs, so it takes values like 5s
, 3m
, etc
@alexkursell please also add an e2e test for configuring |
1f7beab
to
ffeb1fe
Compare
/approve |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: aledbf, alexkursell, ElvinEfendi The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
What this PR does / why we need it: We already support proxy_next_upstream and proxy_next_upstream_tries. We should also support proxy_next_upstream_timeout
This PR adds both a configmap value and annotation,
proxy-next-upstream-timeout
, that mirrors the other two supported proxy settings.