forust
8c0e36a5c0
ci / lint-prettier (push) Skipped
ci / lint-ruff (push) Skipped
ci / lint-yaml (push) Skipped
ci / lint-dockerfiles (push) Skipped
ci / validate (push) Skipped
renovate-ci / validate-renovate (push) Skipped
ci / lint-compose (pull_request) Successful in 11s
ci / lint-actionlint (pull_request) Successful in 6s
ci / lint-shellcheck (pull_request) Successful in 16s
ci / lint-dockerfiles (pull_request) Successful in 6s
ci / lint-prettier (pull_request) Successful in 16s
ci / lint-ruff (pull_request) Successful in 7s
ci / lint-yaml (pull_request) Successful in 10s
ci / validate (pull_request) Successful in 7s
ci / build (pull_request) Skipped
renovate-ci / validate-renovate (pull_request) Failing after 1m40s
18 lines
930 B
Markdown
18 lines
930 B
Markdown
# VictoriaMetrics
|
|
|
|
The `victoria-operator` Helm release converts Prometheus Operator
|
|
`ServiceMonitor` resources into owned `VMServiceScrape` resources. The
|
|
`VMAgent` selects converted scrapes labeled `release: prometheus-stack` in all
|
|
namespaces and writes them to the existing single-node VictoriaMetrics
|
|
instance. Changes to selected `ServiceMonitor` resources are reconciled
|
|
automatically; there is no copied Prometheus scrape-config blob to regenerate.
|
|
|
|
The agent drops targets for the Prometheus server service to avoid duplicating
|
|
its self-scrape. `scraper: victoria` identifies the samples ingested by this
|
|
VMAgent.
|
|
|
|
The VictoriaMetrics Operator chart and its CRDs are installed before the
|
|
Kubernetes manifests by the normal deploy workflow. On a cluster where the
|
|
operator CRDs are not installed yet, CI skips the server-side dry-run of the
|
|
`VMAgent` resource; the deploy installs the chart before applying that resource.
|