-
Notifications
You must be signed in to change notification settings - Fork 1.8k
document all the route annotations and PR11984 #3301
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
Conversation
7fe9b79
to
8274e59
Compare
|
||
By default, a server-side timeout is set across all routes. It is possible to | ||
change that timeout using an annotation in the route configuration. | ||
By default, or using an environment variable a number of configuration options |
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.
Maybe reword this - sounds a bit odd by default or using
- something like Using environment variables as defined in <add-link-to-section>, a router can set the default options for all the routes it exposes. An individual route can choose to override some of these defaults by providing specific configuration via/in (I like via but its normally not used in docs) its annotations
.
@ramr does this clear it up? |
LGTM |
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.
LGTM
@@ -219,6 +220,7 @@ variables on the *deployment config* for the router to alter its configuration. | |||
|`*ROUTER_SUBDOMAIN*`| | The template that should be used to generate the hostname for a route without spec.host (e.g. `${name}-${namespace}.myapps.mycompany.com`). | |||
|`*ROUTER_SYSLOG_ADDRESS*` | | Address to send log messages. Disabled if empty. | |||
|`*ROUTER_TCP_BALANCE_SCHEME*` | source | Load-balancing strategy for multiple endpoints for pass-through routes. Available options are `source`, `roundrobin`, or `leastconn`. | |||
|`*ROUTER_LOAD_BALANCE_ALGORITHM*` | leastconn | Load-balanceing strategy for multiple endpoints for edge and reencrypt terminated routes. Available options are `source`, `roundrobin`, or `leastconn`. |
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.
Load-balanceing => Load-balancing
Doesn't this also apply to http routes?
.Route Annotations | ||
[cols="2*", options="header"] | ||
|=== | ||
|Variable | Description |
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.
Can we sort this section alphabetically by annotation?
[cols="2*", options="header"] | ||
|=== | ||
|Variable | Description | ||
|`*haproxy.router.openshift.io/balance*`| sets the load balance algorithm. Available options are `source`, `roundrobin`, or `leastconn`. |
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.
The first letter of the description should be uppercase to match the other table.
Should we indicate the ENV that provides the default (perhaps in a new column)
load-balancing (or make the pervious one match this case)
|=== | ||
|Variable | Description | ||
|`*haproxy.router.openshift.io/balance*`| sets the load balance algorithm. Available options are `source`, `roundrobin`, or `leastconn`. | ||
|`*haproxy.router.openshift.io/timeout*` | sets a server side timeout. overwrites `*ROUTER_DEFAULT_SERVER_TIMEOUT*` for that route |
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.
server-side
Just make the default env be noted in a new column
|Variable | Description | ||
|`*haproxy.router.openshift.io/balance*`| sets the load balance algorithm. Available options are `source`, `roundrobin`, or `leastconn`. | ||
|`*haproxy.router.openshift.io/timeout*` | sets a server side timeout. overwrites `*ROUTER_DEFAULT_SERVER_TIMEOUT*` for that route | ||
|`*haproxy.router.openshift.io/rate-limit-connections*`| setting to true enables rate limiting functionality |
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.
Should true be in quotes? Or in a fixed width font? What's the style elsewhere?
|`*haproxy.router.openshift.io/balance*`| sets the load balance algorithm. Available options are `source`, `roundrobin`, or `leastconn`. | ||
|`*haproxy.router.openshift.io/timeout*` | sets a server side timeout. overwrites `*ROUTER_DEFAULT_SERVER_TIMEOUT*` for that route | ||
|`*haproxy.router.openshift.io/rate-limit-connections*`| setting to true enables rate limiting functionality | ||
|`*haproxy.router.openshift.io/rate-limit-connections.concurrent-tcp*`| limits the number of concurrent tcp connections shared by an IP address |
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.
TCP? What's the style?
|`*haproxy.router.openshift.io/rate-limit-connections*`| setting to true enables rate limiting functionality | ||
|`*haproxy.router.openshift.io/rate-limit-connections.concurrent-tcp*`| limits the number of concurrent tcp connections shared by an IP address | ||
|`*haproxy.router.openshift.io/rate-limit-connections.rate-tcp*`| limits the rate at which an IP address can make tcp connections | ||
|`*haproxy.router.openshift.io/rate-limit-connections.rate-http*`| limits the rate at which an IP address can make http requests |
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.
HTTP? What's the style?
|`*haproxy.router.openshift.io/rate-limit-connections.concurrent-tcp*`| limits the number of concurrent tcp connections shared by an IP address | ||
|`*haproxy.router.openshift.io/rate-limit-connections.rate-tcp*`| limits the rate at which an IP address can make tcp connections | ||
|`*haproxy.router.openshift.io/rate-limit-connections.rate-http*`| limits the rate at which an IP address can make http requests | ||
|`*haproxy.router.openshift.io/disable_cookies*`| disables the use of cookies, the balance algorithm is used to determine which backend serves connections everytime |
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.
Disables the use of cookies to track related connections. If set to 'true' the balance algorithm is used to choose which back-end serves connections for each HTTP request.
|`*haproxy.router.openshift.io/rate-limit-connections.rate-tcp*`| limits the rate at which an IP address can make tcp connections | ||
|`*haproxy.router.openshift.io/rate-limit-connections.rate-http*`| limits the rate at which an IP address can make http requests | ||
|`*haproxy.router.openshift.io/disable_cookies*`| disables the use of cookies, the balance algorithm is used to determine which backend serves connections everytime | ||
|`*router.openshift.io/haproxy.health.check.interval*`| set the health check interval for backend endpoints |
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.
Sets the interval for the back-end health checks.
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.
LGTM
@JacobTanenbaum What releases should this be for? Please put that in the PR description. @openshift/team-documentation PTAL. This has passed technical review. |
LGTM. I added a to_followup label, as I will make some minor follow-up edits to the topic as a whole in a follow-up PR. @JacobTanenbaum Is this for 3.4? Thanks! |
@JacobTanenbaum Also, can you please give this a squash? |
change log added a referance name to Configuration parameters and reworded the introduction to Route-specific Annotations address a number of issues brought by ben bennet - Load-balanceing => Load-balancing for ROUTER_LOAC_BALANCE_ALGORITHM - sorted annotation table alphabetically - first letter of annotation tables descriptions are uppercase - server side => server-side in description of haproxy.router.openshift.io/timeout - added a column to the annotations for the default env variables they overwrite - changed true to fixed witdth in description of haproxy/openshift.io/rate-limit-connections - changed occurances of tcp, http, https to TCP, HTTP, HTTPS respectivly to conform with style - changed description of haproxy.router.openshift.io/disable_cookies and router.openshift.io/haproxy.health.check.interval
42ac0ab
to
d45d2a4
Compare
@ahardin-rh squashed |
@JacobTanenbaum Thanks! Can you please check my labels? I am assuming this is for 3.4. is that correct? |
@knobunc is this for 3.4 or 3.5? |
@JacobTanenbaum if all of the annotations are in 3.4, then it can be for 3.4. Can you confirm if they are? |
they are in 3.4 |
Thanks! |
[rev_history] |
No description provided.