mirror of
https://github.com/VictoriaMetrics/VictoriaMetrics.git
synced 2024-11-21 14:44:00 +00:00
45cf83cd8f
This reverts commit 92b22581e6.
Reason for revert: too complex and slow approach for spellchecking task.
This approach may significantly slow down development pace. It also may take non-trivial
amounts of additional time and resources at CI/CD because of all this npm shit at cspell directory.
Note to @arkid15r : the idea with the ability to run spellchecker on all the VictoriaMetrics
codebase is great. But this shouldn't be mandatory pre-commit check. It is enough to have
a Makefile rule like `make spellcheck`, which could be run manually whenever spellcheck is needed
(e.g. once per month or once per quarter).
2.2 KiB
2.2 KiB
| sort | weight | title | menu | aliases | |||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| 13 | 13 | Enterprise features |
|
|
Using operator with enterprise features
Operator doesn't have enterprise version for itself, but it supports enterprise features for VictoriaMetrics components:
- VMAgent Enterprise features:
- VMAlert Enterprise features:
- VMAuth Enterprise features
- VMCluster Enterprise features
- VMRule Enterprise features
- VMSingle Enterprise features
- VMUser Enterprise features
More information about enterprise features you can read on VictoriaMetrics Enterprise page.
In order to find examples of deploying enterprise components with operator, please, check this documentation.