Update haproxy configuration to route gitlab-com requests to new canary backends
The current rules for routing requests to canary are:
...
use_backend api if is_gitlab_com_api api_rate_limit_whitelist
use_backend api if is_gitlab_com_api whitelist_internal
use_backend api if is_gitlab_com_api whitelist_api
use_backend api_rate_limit if is_gitlab_com_api
use_backend https_git if is_gitlab_com_https_git
use_backend websockets if is_socket_upg or is_socket_path
use_backend canary_web if is_canary or is_canary_host
default_backend web
...
backend canary_web
mode http
-
create additional canary specific backends for:
- api
- git
- registry
-
Set a canary cookie that defaults to true if a request goes to gitlab-com/
-
Create a new condition for each canary backend that only uses them if they are healthy
Edited by John Jarvis