MCPcopy Create free account
hub / github.com/VictoriaMetrics/operator

github.com/VictoriaMetrics/operator

Chat with this repo
repository ↗ · DeepWiki ↗ · release v0.73.1 ↗ · + Follow · compare 2 versions
4,599 symbols 16,309 edges 508 files 2,710 documented · 59% updated 7d agov0.68.6 · 2026-06-25★ 57532 open issues

Browse by type

Functions 3,591 Types & classes 1,008
What it actually does AI analysis from the code graph — generated when you open this
loading…
README

Latest Release Docker Pulls Slack GitHub license Go Report Build and Test Status

VictoriaMetrics logo

VictoriaMetrics operator

Overview

Design and implementation inspired by prometheus-operator. It's great a tool for managing monitoring configuration of your applications. VictoriaMetrics operator has api capability with it. So you can use familiar CRD objects: ServiceMonitor, PodMonitor, PrometheusRule, Probe and ScrapeConfig. Or you can use VictoriaMetrics CRDs:

  • VMServiceScrape - defines scraping metrics configuration from pods backed by services.
  • VMPodScrape - defines scraping metrics configuration from pods.
  • VMRule - defines alerting or recording rules.
  • VMProbe - defines a probing configuration for targets with blackbox exporter.
  • VMScrapeConfig - define a scrape config using any of the service discovery options supported in victoriametrics.

Besides, operator allows you to manage VictoriaMetrics applications inside kubernetes cluster and simplifies this process quick-start With CRD (Custom Resource Definition) you can define application configuration and apply it to your cluster crd-objects.

Operator simplifies VictoriaMetrics cluster installation, upgrading and managing.

It has integration with VictoriaMetrics vmbackupmanager - advanced tools for making backups. Check Backup automation for VMSingle or Backup automation for VMCluster.

Use cases

For kubernetes-cluster administrators, it simplifies installation, configuration, management for VictoriaMetrics application. And the main feature of operator - is ability to delegate applications monitoring configuration to the end-users.

For applications developers, its great possibility for managing observability of applications. You can define metrics scraping and alerting configuration for your application and manage it with an application deployment process. Just define app_deployment.yaml, app_vmpodscrape.yaml and app_vmrule.yaml. That's it, you can apply it to a kubernetes cluster. Check quick-start for an example.

Operator vs helm-chart

VictoriaMetrics provides helm charts. Operator makes the same, simplifies it and provides advanced features.

Documentation

  • quick start doc
  • high availability doc
  • relabeling configuration doc
  • managing crd objects versions doc
  • design and description of implementation design
  • operator objects description doc
  • backups docs
  • external access to cluster resourcesdoc
  • security doc
  • resource validation doc

Configuration

Operator configured by env variables, list of it can be found at link

It defines default configuration options, like images for components, timeouts, features.

Kubernetes' compatibility versions

operator tested on officially supported Kubernetes versions

Community and contributions

Feel free asking any questions regarding VictoriaMetrics:

Development

Dependencies:

  • kubebuilder v4
  • golang 1.23+
  • kubectl
  • docker

start:

make run

to run unit tests

make test

to run e2e tests on automatically configured Kind cluster

# make test-e2e

Extension points exported contracts — how you extend this code

Core symbols most depended-on inside this repo

Shape

Method 2,333
Function 1,258
Struct 749
Interface 214
TypeAlias 42
FuncType 3

Languages

Go100%
Python1%

Modules by API surface

api/operator/v1beta1/zz_generated.deepcopy.go488 symbols
api/operator/v1/zz_generated.deepcopy.go118 symbols
api/operator/v1beta1/vmalertmanagerconfig_types.go105 symbols
api/operator/v1beta1/vmextra_types.go97 symbols
api/operator/v1beta1/vmcluster_types.go82 symbols
api/operator/v1/vlcluster_types.go64 symbols
api/operator/v1/vtcluster_types.go59 symbols
api/operator/v1beta1/vmagent_types.go52 symbols
api/operator/v1beta1/vmauth_types.go51 symbols
api/operator/v1beta1/vmalertmanager_types.go47 symbols
api/operator/v1/vmanomaly_types.go47 symbols
internal/controller/operator/factory/vmanomaly/config/models.go46 symbols

Dependencies from manifests, versioned

github.com/VictoriaMetrics/VictoriaLogsv1.51.1-0.2026062406 · 1×
github.com/VictoriaMetrics/easyprotov1.2.0 · 1×
github.com/armon/go-metricsv0.4.1 · 1×
github.com/aws/aws-sdk-go-v2v1.42.0 · 1×
github.com/aws/aws-sdk-go-v2/configv1.32.25 · 1×
github.com/aws/aws-sdk-go-v2/credentialsv1.19.24 · 1×
github.com/aws/aws-sdk-go-v2/feature/ec2/imdsv1.18.29 · 1×

For agents

$ claude mcp add operator \
  -- python -m otcore.mcp_server <graph>

⬇ download graph artifact

Ask about this repo answers extend the page