diff options
Diffstat (limited to 'doc/operations/feature_flags.md')
| -rw-r--r-- | doc/operations/feature_flags.md | 25 |
1 files changed, 13 insertions, 12 deletions
diff --git a/doc/operations/feature_flags.md b/doc/operations/feature_flags.md index 5fd497a79e1..fe21f0db1c7 100644 --- a/doc/operations/feature_flags.md +++ b/doc/operations/feature_flags.md @@ -24,8 +24,7 @@ To contribute to the development of the GitLab product, view ## How it works -GitLab uses [Unleash](https://github.com/Unleash/unleash), a feature -toggle service. +GitLab offers an [Unleash](https://github.com/Unleash/unleash)-compatible API for feature flags. By enabling or disabling a flag in GitLab, your application can determine which features to enable or disable. @@ -76,10 +75,9 @@ is 200. For GitLab SaaS, the maximum number is determined by [tier](https://abou You can apply a feature flag strategy across multiple environments, without defining the strategy multiple times. -GitLab feature flags use [Unleash](https://docs.getunleash.io/) as the feature flag -engine. In Unleash, there are [strategies](https://docs.getunleash.io/reference/activation-strategies) -for granular feature flag controls. GitLab feature flags can have multiple strategies, -and the supported strategies are: +GitLab feature flags are based on [Unleash](https://docs.getunleash.io/). In Unleash, there are +[strategies](https://docs.getunleash.io/reference/activation-strategies) for granular feature +flag controls. GitLab feature flags can have multiple strategies, and the supported strategies are: - [All users](#all-users) - [Percent of Users](#percent-of-users) @@ -372,7 +370,11 @@ end ### Unleash Proxy example As of [Unleash Proxy](https://docs.getunleash.io/reference/unleash-proxy) version -0.2, the proxy is compatible with feature flags. To run a Docker container to +0.2, the proxy is compatible with feature flags. + +You should use Unleash Proxy for production on GitLab.com. See the [performance note](#maximum-supported-clients-in-application-nodes) for details. + +To run a Docker container to connect to your project's feature flags, run the following command: ```shell @@ -418,10 +420,8 @@ Read [How it works](#how-it-works) section before diving into the details. ### Maximum supported clients in application nodes -GitLab accepts client requests as much as possible until it hits the [rate limiting](../security/rate_limits.md). -At the moment, the feature flag API falls into **Unauthenticated traffic (from a given IP address)** -in the [GitLab.com specific limits](../user/gitlab_com/index.md), -so it's **500 requests per minute**. +GitLab accepts as many client requests as possible until it hits the [rate limit](../security/rate_limits.md). +The feature flag API is considered **Unauthenticated traffic (from a given IP address)**. For GitLab.com, see the [GitLab.com specific limits](../user/gitlab_com/index.md). The polling rate is configurable in SDKs. Provided that all clients are requesting from the same IP: @@ -429,7 +429,8 @@ The polling rate is configurable in SDKs. Provided that all clients are requesti - Request once per 15 sec ... 125 clients can be supported. For applications looking for more scalable solution, you should use [Unleash Proxy](#unleash-proxy-example). -This proxy server sits between the server and clients. It requests to the server as a behalf of the client groups, +On GitLab.com, you should use Unleash Proxy to reduce the chance of being rate limited across endpoints. +This proxy server sits between the server and clients. It makes requests to the server on behalf of the client groups, so the number of outbound requests can be greatly reduced. There is also an [issue](https://gitlab.com/gitlab-org/gitlab/-/issues/295472) to give more |