mirror of
https://github.com/Unleash/unleash.git
synced 2024-10-28 19:06:12 +01:00
7f7891dc8e
Adds a note to the resource limit docs about what resources have a minimum limit of 1. Also updates the availability note in preparation for 6.2 GA --------- Co-authored-by: Melinda Fekete <melinda.fekete@getunleash.io>
57 lines
4.4 KiB
Plaintext
57 lines
4.4 KiB
Plaintext
---
|
|
title: Resource Limits
|
|
---
|
|
import Figure from '@site/src/components/Figure/Figure.tsx'
|
|
|
|
:::note Availability
|
|
**Version**: `6.2+`
|
|
:::
|
|
|
|
<Figure caption="When you're close to reaching the limit for a resource, you'll see a warning in the Unleash UI. The warning will tell you what the limit is, how close you are to reaching it, and how you can increase the limit." img="/img/project-limit-warning.png" />
|
|
|
|
To ensure that Unleash operates smoothly, it includes resource limits for some of the key resources that you can create. The limit for each resource can vary between the different Unleash plans.
|
|
|
|
The resources and their respective limits and environment variables are:
|
|
|
|
| Resource | OSS limit | Pro limit | Enterprise limit | Environment variable |
|
|
|-----------------------------------------------------------------|----------:|----------:|-----------------:|------------------------------------------------|
|
|
| [Feature flags](feature-toggles.mdx)[^1] | 5,000 | 5,000 | 50,000 | `UNLEASH_FEATURE_FLAGS_LIMIT` |
|
|
| [Strategies](activation-strategies.md) per flag per environment | 30 | 30 | 30 | `UNLEASH_FEATURE_ENVIRONMENT_STRATEGIES_LIMIT` |
|
|
| [Constraints](strategy-constraints.md) per strategy | 30 | 30 | 30 | `UNLEASH_CONSTRAINTS_LIMIT` |
|
|
| Values per [constraint](strategy-constraints.md) | 250 | 250 | 1,000 | `UNLEASH_CONSTRAINT_VALUES_LIMIT` |
|
|
| [Segments](segments.mdx) | 300 | 300 | 300 | `UNLEASH_SEGMENTS_LIMIT` |
|
|
| [API tokens](api-tokens-and-client-keys.mdx) | 2,000 | 2,000 | 2,000 | `UNLEASH_API_TOKENS_LIMIT` |
|
|
| [Projects](projects.md) | 1 | 3 | 500 | `UNLEASH_PROJECTS_LIMIT` |
|
|
| [Environments](environments.md) | 2 | 2 | 50 | `UNLEASH_ENVIRONMENTS_LIMIT` |
|
|
| [Signal](signals.md) endpoints | N/A | N/A | 5 | `UNLEASH_SIGNAL_ENDPOINTS_LIMIT` |
|
|
| [Signal](signals.md) tokens per endpoint | N/A | N/A | 5 | `UNLEASH_SIGNAL_TOKENS_PER_ENDPOINT_LIMIT` |
|
|
| [Action](actions.md) set actions | N/A | N/A | 10 | `UNLEASH_ACTION_SET_ACTIONS_LIMIT` |
|
|
| [Action](actions.md) sets per project | N/A | N/A | 5 | `UNLEASH_ACTION_SETS_PER_PROJECT_LIMIT` |
|
|
| [Action](actions.md) set filters | N/A | N/A | 5 | `UNLEASH_ACTION_SET_FILTERS_LIMIT` |
|
|
| [Action](actions.md) set filter values | N/A | N/A | 25 | `UNLEASH_ACTION_SET_FILTER_VALUES_LIMIT` |
|
|
|
|
## Overriding the limits
|
|
|
|
:::info Existing customers above the limits
|
|
Existing hosted customers who are already above the limits will have their limits adjusted to 110% of their maximum values when the limits were introduced.
|
|
:::
|
|
|
|
With a few exceptions, all the limits can be overridden through the use of their respective environment variables. However, while it is possible to override these limits, we advise against it in most cases. If you feel that you're unable to do what you need to do because of the limits, we'd love to hear from you.
|
|
|
|
The following resources have a lower limit of 1:
|
|
- feature flags
|
|
- strategies
|
|
- constraint values
|
|
- projects
|
|
- environments
|
|
|
|
If you try to set their limits lower than that, Unleash will automatically adjust them to 1.
|
|
|
|
If you operate a self-hosted Unleash instance, you can adjust the limit yourself. For hosted users of Unleash, you'll need to reach out and talk to your Unleash contact.
|
|
|
|
The only limits that can't be changed, are
|
|
- the limits for projects and environments for OSS instances
|
|
- the limits for projects and environments for Pro instances
|
|
|
|
[^1]: Archived feature flags do not count towards your feature flag total. The limit only applies to active (i.e. not archived) feature flags.
|